Updated release workflow and reverted changes from last failed publish #151
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: edaddc2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
diegopinate
previously approved these changes
Jan 17, 2025
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.
Added debugging output after release action and adjusted flags for release action.
Fixes the publishing issue. Trigger must be on pushes to master only.
When a Pr gets merged into the master, that causes a version update, i.e., has a changeset.
A workflow will pick up and create a release branch if not already created.
The release branch will version the package and update the change log. Once the release branch merges into the master again, a package update will be detected, a tag and release will be created, and the npm package will be published.
If the release branch is present and active and new changes are merged into the master from the dev branches, the release branch will be updated, and no package release will be triggered until the release branch is merged.
The error causing the failure was due to a manual trigger. This is supposed to work off pushes to master only. So, I removed the manual trigger and added debugging logs.