Skip to content

CLI: Support upgrading to canary versions#25596

Merged
JReinhold merged 10 commits into
nextfrom
jeppe/versioned-canary-sandbox
Jan 15, 2024
Merged

CLI: Support upgrading to canary versions#25596
JReinhold merged 10 commits into
nextfrom
jeppe/versioned-canary-sandbox

Conversation

@JReinhold
Copy link
Copy Markdown
Contributor

@JReinhold JReinhold commented Jan 15, 2024

Works on #25293

What I did

Fixed a small bug where it would never be possible to upgrade to a canary version because it's a lower version number. Now canaries are always allowed. We also don't add a caret to the version specifier when upgrading to a canary.

Added information about using a canary release with sandbox or upgrade. Left out init because it didn't seem relevant although technically possible.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This pull request has been released as version 0.0.0-pr-25596-sha-579fbffd. Install it by pinning all your Storybook dependencies to that version.

More information
Published version 0.0.0-pr-25596-sha-579fbffd
Triggered by @JReinhold
Repository storybookjs/storybook
Branch jeppe/versioned-canary-sandbox
Commit 579fbffd
Datetime Mon Jan 15 09:45:31 UTC 2024 (1705311931)
Workflow run 7527034203

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=25596

@JReinhold JReinhold added cli build Internal-facing build tooling & test updates ci:docs Run the CI jobs for documentation checks only. labels Jan 15, 2024
@JReinhold JReinhold self-assigned this Jan 15, 2024
@JReinhold JReinhold changed the title GitHub: Add canary sandbox and upgrade information to PR descriptions CLI: Support upgrading to canary versions Jan 15, 2024
@JReinhold JReinhold added maintenance User-facing maintenance tasks ci:normal Run our default set of CI jobs (choose this for most PRs). and removed build Internal-facing build tooling & test updates ci:docs Run the CI jobs for documentation checks only. labels Jan 15, 2024
@JReinhold JReinhold merged commit f091347 into next Jan 15, 2024
@JReinhold JReinhold deleted the jeppe/versioned-canary-sandbox branch January 15, 2024 14:56
@github-actions github-actions Bot mentioned this pull request Jan 15, 2024
21 tasks
JReinhold added a commit that referenced this pull request Jan 15, 2024
…dbox

CLI: Support upgrading to canary versions
(cherry picked from commit f091347)
@github-actions github-actions Bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:normal Run our default set of CI jobs (choose this for most PRs). cli maintenance User-facing maintenance tasks patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants