Conversation
Baseline @spectrum-web-components/core and @adobe/spectrum-wc to the 2.0.0 major line and enter Changesets pre-release mode (tag: beta) so 2nd-gen betas are cut as semver-correct 2.0.0-beta.N, leading up to a clean 2.0.0 GA. Co-authored-by: Cursor <cursoragent@cursor.com>
🦋 Changeset detectedLatest commit: 8b4f297 The changes in this PR will be included in the next version bump. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
Co-authored-by: Cursor <cursoragent@cursor.com>
Add a manual `scope` input (all | 2nd-gen) to the Publish Packages workflow so a private beta of the 2nd-gen packages can be cut on demand without releasing 1st-gen. When scope is `2nd-gen`, only @spectrum-web-components/core (OIDC trusted publishing) and @adobe/spectrum-wc (npm token) are packed and published under the chosen pre-release dist-tag; 1st-gen steps and React wrappers are skipped, and the `latest` tag is rejected for this scope. The default `all` scope and the automatic push-to-main `next` release are unchanged. Co-authored-by: Cursor <cursoragent@cursor.com> (cherry picked from commit 5169fc4)
Allow the 2nd-gen-only scope to run with npm publish --dry-run so the build, version, and pack steps can be validated from a feature branch without writing to the npm registry. Co-authored-by: Cursor <cursoragent@cursor.com> (cherry picked from commit 9626abc)
The check-changesets step runs under `bash -e`, so the package-detection grep aborted the job whenever a changeset referenced only @spectrum-web-components/core (grep -v matches nothing and exits 1). Add `|| true` so core-only and @adobe-only changesets are handled. Co-authored-by: Cursor <cursoragent@cursor.com> (cherry picked from commit b8f8fcf)
…-release versions For the 2nd-gen beta scope, publish the versions already committed on the pre-release branch (2.0.0-beta.N) instead of letting `changeset version --snapshot` overwrite them with a timestamped snapshot. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Puts the 2nd-gen packages into Changesets pre-release mode (dist-tag
beta) on a dedicated, long-livedgen2-betarelease branch, and baselines them onto the2.0.0major line.After this change,
@spectrum-web-components/coreand@adobe/spectrum-wcare versioned as2.0.0-beta.0; subsequent releases increment2.0.0-beta.N, leading up to a clean2.0.0GA viachangeset pre exit.Motivation and context
We're running a private 2nd-gen beta (through ~mid-July). The requirements:
betadist-tag, kept separate from 1st-gen'snext.2.0.0-beta.0 → 2.0.0-beta.1 → …) rather than:0.0.0-beta-<datetime>) — unordered, not a real release line, or0.xline — per semver this signals "initial development, anything may change" (item 4), which understates how stable 2nd-gen actually is. A-betapre-release of2.0.0(item 9) is the accurate signal.2.0.0for GA.Changesets pre-release mode delivers exactly this. Because
coreand@adobe/spectrum-wcare a linked group currently on0.x, we baseline them to1.0.0and add a singlemajorchangeset so the bump resolves to2.0.0. Pre mode then holds the base at2.0.0and only advances the-beta.Ncounter on each release.What changed
@spectrum-web-components/coreand@adobe/spectrum-wc→2.0.0-beta.0(linked, in lockstep).@adobe/spectrum-wc's internal@spectrum-web-components/coredependency →2.0.0-beta.0..changeset/pre.json("mode": "pre","tag": "beta").majorchangeset for the Gen2 2.0.0 milestone.yarn.lockcoredescriptor.@spectrum-web-components/2nd-genis intentionally untouched — it isprivate: truewith noexports/files(workspace root only) and is never published.How to verify
On this branch:
@spectrum-web-components/coreand@adobe/spectrum-wcpackage.jsonversions are2.0.0-beta.0.@spectrum-web-components/coredependency is2.0.0-beta.0.## 2.0.0-beta.0; swc's "Updated dependencies" citescore@2.0.0-beta.0.yarn.lockshows@spectrum-web-components/core@npm:2.0.0-beta.0..changeset/pre.jsonexists withmode: pre,tag: beta.Reproduce the version progression in a throwaway worktree (no risk to
main):pre enter beta+version2.0.0-beta.02.0.0-beta.0version2.0.0-beta.1version2.0.0-beta.2pre exit+version2.0.02.0.0Not in this PR (follow-ups)
publish.ymlworkflow onmainrunschangeset version --snapshotfor non-latesttags, which would clobber the committed2.0.0-beta.0. Releasing the real beta uses thescope=2nd-genpublish path (packs frompackage.json+npm publish --tag beta, no re-version) and needs the "skipchangeset versionforscope=2nd-gen" gate. Tracked separately.pre.jsonexists, everychangeset versionproduces a beta — do not run a normal release from it withoutchangeset pre exitfirst.Related issue(s)
<ADD TICKET NUMBER — do not link, per Adobe guidance>Author's checklist
majorchangeset).gen2-beta-release-strategy.mdshared separately.)Manual review / Device review / Accessibility testing
N/A — this PR changes only release versioning configuration (Changesets pre-release mode + version baselines). There is no UI, DOM, focus, or screen-reader surface affected, and no runtime code paths change. Reviewers should focus on the versioning/changeset correctness above.