-
Notifications
You must be signed in to change notification settings - Fork 18
chore: migrate CI to GHA and publish to npm with OIDC #1003
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
- Removed CircleCI configuration file. - Added multiple GitHub Actions workflows for build, checks, and release processes. - Implemented caching for build artifacts and dependencies. - Updated permissions for GitHub Actions to manage secrets and perform necessary actions.
- remove test-oidc-trusted-publishing config for releases
elylucasctfl
previously approved these changes
Nov 13, 2025
elylucasctfl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a reminder to take out the test branch from the main.yaml, if you need another ✅ with that change let me know.
- Remove write permissions for pull-requests in dependabot workflow - Updated permissions for the lint job in check.yaml to allow read access to contents. - Changed Node.js version from 18 to 22 in check.yaml. - Modified release job conditions in main.yaml to exclude the 'test-oidc-trusted-publishing' branch.
- Changed the method for retrieving the latest release tag from GitHub API to using `git describe --tags --abbrev=0`.
…nhance semantic-release configuration - Updated Node.js version from 22 to 24 in build, check, and release workflows. - Enhanced semantic-release configuration by adding release rules for build scope dependencies.
ethan-ozelius-contentful
approved these changes
Nov 14, 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.
Note
There were 618 commits since Nov '23 without a release (mostly dependabot commits). I've added a release rule for commits with
build(deps)which should cause a release on those commits to master. Upon first release after this GHA migration, the release should succeed, but the release step will show failed. This is due to the 618 commits. The semantic-release/github process reaches out to GH's GraphQL api to get commit data, but times out, hence the failed status. More details in DX-544.Summary