fix(ci): create monorepo v* tags and GitHub Releases instead of per-package changeset tags#237
Open
Winify wants to merge 3 commits into
Open
fix(ci): create monorepo v* tags and GitHub Releases instead of per-package changeset tags#237Winify wants to merge 3 commits into
Winify wants to merge 3 commits into
Conversation
Changeset publish creates per-package tags (@scope/name@version). This repo uses monorepo-level v* tags (keyed to @wdio/devtools-service version) and GitHub Releases. The updated workflow: - Pushes the version commit without --follow-tags (per-package tags stay local) - Creates a v<service-version> tag and pushes it - Creates a GitHub Release with package bump summary + auto-generated notes - Deletes per-package tags locally and from the remote
03b2573 to
a627c98
Compare
d10383b to
df13873
Compare
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
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.
What & why
The release workflow was recently converted to changesets. Changesets creates per-package tags (
@wdio/nightwatch-devtools@1.4.0) and doesn't create GitHub Releases. This repo uses monorepo-levelv*tags (keyed to@wdio/devtools-serviceversion) with GitHub Releases.Changes
--follow-tags: Per-package tags created by changesets stay local and are deleted after usev<service-version>tag: Drives the monorepo tag from@wdio/devtools-serviceversion (continuity with existingv10.xseries)gh release createwith--generate-notes(auto-generated PR notes) prepended with a package bump summaryType of change
Packages touched
shared(types and contracts)core(framework-agnostic capture/reporting)service(WebdriverIO adapter)nightwatch-devtools(Nightwatch adapter)selenium-devtools(Selenium adapter)backend(server)app(UI)script(page-injected runtime)Notes for reviewers
The previous release (workflow run 27951318411) created a per-package tag
@wdio/nightwatch-devtools@1.4.0. That tag has been cleaned up and replaced withv10.6.1+ a GitHub Release. Theorigin/mainbranch also needs to be fast-forwarded to include the RELEASING commit (currently 10 commits behind local main).🤖 Generated with Claude Code