chore(tooling): adapt publishing workflow for new monorepo structure #5851

rubencarvalho · 2025-11-02T21:47:50Z

Description

This PR streamlines and fixes the publishing workflow for Spectrum Web Components after the monorepo restructure.

Most relevant changes

Unified publish script (`scripts/publish.js`)

Handles both 1st-gen and 2nd-gen packages in a single workflow.
Cleans and rebuilds everything from scratch to prevent stale artifact issues.
Publishes React wrappers directly via npm.
Properly handles snapshot vs regular releases.

Fixed global changelog generator

Corrected regex to detect @spectrum-web-components/core changes (previously looked for @swc/core).
Now only runs for regular releases (not snapshots).
Runs before changeset version to access changeset files before deletion.

Updated build configuration aliases

Fixed alias @swc/core → @spectrum-web-components/core in:
- 1st-gen/web-test-runner.config.js
- 1st-gen/test/visual/rollup.config.js
- 1st-gen/projects/documentation/rollup.config.js

Fixed Yarn constraints for new monorepo structure

Updated glob patterns:

- {packages,tools}/*
+ {1st-gen/{packages,tools},2nd-gen/packages}/*

Fixed folder name extraction for component name resolution.
Added generation-specific rules:
- 1st-gen: main/module → ./src/index.js
- 2nd-gen: main/module → ./dist/index.js
Ensured both generations set publishConfig.access: "public".

Cleaned up obsolete scripts from `1st-gen/package.json`

Removed:

changeset-publish
changeset-snapshot-publish
prepublishOnly, postpublish
prepublish:react, postpublish:react, publish:react
push-to-remote

Updated release documentation

Simplified workflow steps in
CONTRIBUTOR-DOCS/01_contributor-guides/06_releasing-swc.md
Documented that the script automatically handles all cleaning and building.
Added custom tag usage examples (nightly, beta, etc.).

Motivation and context

After reorganizing the repository into 1st-gen/ and 2nd-gen/ subdirectories, the publishing workflow needed to be updated.

Author's checklist

I have read the CONTRIBUTING and PULL_REQUESTS documents.
I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
I have added automated tests to cover my changes.
I have included a well-written changeset if my change needs to be published.
I have included updated documentation if my change required it.

Reviewer's checklist

Includes a Github Issue with appropriate flag or Jira ticket number without a link
Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
Automated tests cover all use cases and follow best practices for writing
Validated on all supported browsers
All VRTs are approved before the author can update Golden Hash

Manual review test cases

To be tested under the barebones testing and validation steps.

…ucture Refactors the publishing and release management workflow to support the dual-generation monorepo architecture: - Update Changesets configuration to recognize both 1st-gen and 2nd-gen workspaces, enabling independent versioning strategies - Refactor release scripts to delegate to generation-specific publishing workflows rather than operating on a flat package structure - Update CI/CD publishing jobs to build, test, and publish both generations with appropriate dependency handling for the shared Core library - Preserve existing 1st-gen package publishing behavior to avoid disruption to current consumers This workflow enables continuous delivery of improvements to 1st-gen customers while supporting independent 2nd-gen package releases.

changeset-bot · 2025-11-02T21:47:54Z

⚠️ No Changeset found

Latest commit: 87ff985

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

github-actions · 2025-11-02T21:50:08Z

📚 Branch Preview

🔍 Visual Regression Test Results

When 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: pr-5851

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

github-actions · 2025-11-02T21:53:37Z

Tachometer results

Currently, no packages are changed by this PR...

rubencarvalho · 2025-11-03T09:03:39Z

.nvmrc

@@ -1 +1 @@
-20.13.1
+20.19.0


Bumping minimum version for Storybook 10 compatibility.

rubencarvalho · 2025-11-03T09:03:59Z

1st-gen/package.json

        "build": "wireit",
-        "prebuild": "wireit",
-        "build:clear-cache": "rimraf packages/*/tsconfig.tsbuildinfo && rimraf tools/*/tsconfig.tsbuildinfo",
+        "build:clear-cache": "rimraf .wireit && rimraf packages/*/tsconfig.tsbuildinfo && rimraf tools/*/tsconfig.tsbuildinfo",


Cleaning .wireit cache too.

rubencarvalho · 2025-11-03T09:04:17Z

1st-gen/package.json

        "postpack": "pinst --enable",
-        "postpublish": "yarn prepublish:react && yarn publish:react && yarn postpublish:react",
-        "postpublish:react": "git reset --hard HEAD^ && git prune && rimraf react",
+        "prebuild": "wireit",


This is not new, just got re-ordered.

rubencarvalho · 2025-11-03T09:04:22Z

1st-gen/package.json

        "chromatic": "chromatic --build-script-name storybook:build # note that --project-token must be set in your env variables",
        "create-git-tag": "node --no-warnings ./scripts/create-git-tag.js",
        "custom-element-json": "node ./scripts/custom-element-json.js",
+        "dev:core": "yarn workspace @spectrum-web-components/core dev",


This is not new, just got re-ordered.

rubencarvalho · 2025-11-03T09:04:46Z

1st-gen/package.json

        "@changesets/cli": "2.29.7",
        "@commitlint/cli": "19.8.1",
-        "@commitlint/config-conventional": "^19.8.1",
+        "@commitlint/config-conventional": "19.8.1",


Pinning versions.

rubencarvalho · 2025-11-03T09:20:36Z

1st-gen/tools/base/src/version.js

This needs to stay!!

rubencarvalho · 2025-11-03T09:21:21Z

2nd-gen/README.md

Simplify documentation which will eventually live under Contributing Docs, but this clean version can be useful if you are navigating the GitHub UI and open this folder.

rubencarvalho · 2025-11-03T09:21:44Z

2nd-gen/package.json

Updated commands to consistently run with npm-run-all

rubencarvalho · 2025-11-03T09:22:02Z

2nd-gen/packages/core/README.md

Simple Readme to be shown either in GitHub or npm

rubencarvalho · 2025-11-03T09:22:36Z

CONTRIBUTOR-DOCS/01_contributor-guides/06_releasing-swc.md

Update documentation around releasing to be in sync with new publish script

Rajdeepc · 2025-11-03T05:48:15Z

1st-gen/package.json

-    "engines": {
-        "node": ">=20",
-        "yarn": ">=4.6.0"
-    },


Any reason to remove this?

Rajdeepc · 2025-11-03T06:59:18Z

1st-gen/tools/base/src/version.js

-// Generated by genversion.
-export const version = '1.9.0';


Many consumers still uses this path to version check their packages.

Re-added it

Rajdeepc · 2025-11-03T07:00:22Z

1st-gen/tools/base/test/base.test.ts

 import { SpectrumElement } from '@spectrum-web-components/base';
 import { elementUpdated, expect, fixture, html } from '@open-wc/testing';
-import { version } from '@spectrum-web-components/base/src/version.js';
+import { version } from '@spectrum-web-components/core/shared/base/version.js';


note: Downstream customers needs to update to the new path. Should surface this information up as a breaking change?

Updated to re-export the 2nd-gen one!

…5851) * chore: update and streamline publishing workflow for new monorepo structure Refactors the publishing and release management workflow to support the dual-generation monorepo architecture: - Update Changesets configuration to recognize both 1st-gen and 2nd-gen workspaces, enabling independent versioning strategies - Refactor release scripts to delegate to generation-specific publishing workflows rather than operating on a flat package structure - Update CI/CD publishing jobs to build, test, and publish both generations with appropriate dependency handling for the shared Core library - Preserve existing 1st-gen package publishing behavior to avoid disruption to current consumers This workflow enables continuous delivery of improvements to 1st-gen customers while supporting independent 2nd-gen package releases.

rubencarvalho marked this pull request as ready for review November 2, 2025 21:47

rubencarvalho requested a review from a team as a code owner November 2, 2025 21:47

rubencarvalho added Status: Ready for review PR ready for review or re-review. 2nd gen These issues or PRs map to our 2nd generation work to modernizing infrastructure. High priority PR review PR is a high priority and should be reviewed ASAP labels Nov 2, 2025

rubencarvalho added 5 commits November 3, 2025 08:11

chore: skip flaky picker story

89cb380

chore: update 2nd-gen READMEs

f9e67bc

chore: update golden images cache

fe65f32

chore: infer snapshot usage from tag

33aa554

chore: update publishing documentation

5722ab6

rubencarvalho commented Nov 3, 2025

View reviewed changes

chore: re-add version.js in 1st-gen to gurarantee backward compatibility

f4e2ac6

TarunAdobe approved these changes Nov 3, 2025

View reviewed changes

Rajdeepc requested changes Nov 3, 2025

View reviewed changes

chore: re-add version.js imports and checks

87ff985

Rajdeepc approved these changes Nov 3, 2025

View reviewed changes

rubencarvalho merged commit 3ff495e into barebones Nov 3, 2025
22 checks passed

rubencarvalho deleted the ruben/barbeones-publish-updates branch November 3, 2025 14:39

		@@ -1 +1 @@
		20.13.1 No newline at end of file
		20.19.0 No newline at end of file

chore(tooling): adapt publishing workflow for new monorepo structure #5851

chore(tooling): adapt publishing workflow for new monorepo structure #5851

Uh oh!

Conversation

rubencarvalho commented Nov 2, 2025

Description

Most relevant changes

Unified publish script (scripts/publish.js)

Fixed global changelog generator

Updated build configuration aliases

Fixed Yarn constraints for new monorepo structure

Cleaned up obsolete scripts from 1st-gen/package.json

Updated release documentation

Motivation and context

Author's checklist

Reviewer's checklist

Manual review test cases

Uh oh!

changeset-bot bot commented Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

github-actions bot commented Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Branch Preview

🔍 Visual Regression Test Results

Uh oh!

github-actions bot commented Nov 2, 2025

Tachometer results

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rubencarvalho Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Unified publish script (`scripts/publish.js`)

Cleaned up obsolete scripts from `1st-gen/package.json`

changeset-bot bot commented Nov 2, 2025 •

edited

Loading

github-actions bot commented Nov 2, 2025 •

edited

Loading

rubencarvalho Nov 3, 2025 •

edited

Loading