Skip to content

ci: replace changesets with release-please#739

Open
jkongie wants to merge 1 commit intomainfrom
release-please-implementation
Open

ci: replace changesets with release-please#739
jkongie wants to merge 1 commit intomainfrom
release-please-implementation

Conversation

@jkongie
Copy link
Copy Markdown
Collaborator

@jkongie jkongie commented May 7, 2026

No description provided.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 7, 2026

⚠️ No Changeset found

Latest commit: 6f9c7a2

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

@jkongie jkongie marked this pull request as ready for review May 8, 2026 07:23
@jkongie jkongie requested a review from a team as a code owner May 8, 2026 07:23
Copilot AI review requested due to automatic review settings May 8, 2026 07:23
aws-region: ${{ secrets.AWS_REGION }}
aws-role-arn: ${{ secrets.AWS_OIDC_MCMS_CI_CHANGESET_TOKEN_ISSUER_ROLE_ARN }}
aws-lambda-url: ${{ secrets.GATI_LAMBDA_DEPLOYMENT_AUTOMATION_URL }}
# cd-release:
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just leaving these commented out for now while we test the new release process

@jkongie jkongie force-pushed the release-please-implementation branch 2 times, most recently from f13d105 to 88560e0 Compare May 8, 2026 07:29
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Migrates the repository’s release automation from Changesets to Release Please by adding Release Please configuration/workflows and updating contributor/release documentation accordingly.

Changes:

  • Add Release Please workflow plus release-please-config.json and .release-please-manifest.json.
  • Update RELEASE.md / CONTRIBUTING.md guidance to rely on Conventional Commit PR titles instead of Changesets.
  • Disable (via comments) existing Changesets-driven and tag-driven release publishing steps in GitHub workflows.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
RELEASE.md Rewrites release documentation to describe Release Please + Conventional Commits.
CONTRIBUTING.md Removes Changesets contribution steps and updates PR title guidance/team reference.
release-please-config.json Adds Release Please configuration (go release type + changelog sections).
.release-please-manifest.json Introduces Release Please manifest with the “current” version.
.github/workflows/release-please.yml Adds workflow to open/maintain Release Please PRs and create releases/tags on merge.
.github/workflows/push-tag-release.yml Comments out prior publish + Slack notification jobs for tag pushes.
.github/workflows/push-main.yml Comments out the old Changesets CD job; adjusts Solana cache key formatting.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .release-please-manifest.json Outdated
@@ -0,0 +1,3 @@
{
".": "0.42.1"
Comment on lines +109 to +110
key: "${{
runner.os}}-mcms-contracts-${{steps.solana-programs-cache-key.outputs.key }}"
Comment thread RELEASE.md
## Release Please

After every PR with a changeset is merged, a changesets CI job will create or update a "Version Packages" PR, which contains the release version and information about the changes.
This repo uses [Release Please](https://github.com/googleapis/release-please) to manage releases. Do not run `pnpm changeset` or add changeset files for releases.
Comment on lines +46 to +55
# cicd-publish-release:
# runs-on: ubuntu-latest
# permissions:
# id-token: write
# contents: write
# actions: read
# steps:
# - name: cicd-publish-release
# uses: smartcontractkit/.github/actions/cicd-build-publish-artifacts-go@b4737861584f88fa9569d6978f70fedf8b1ae67c # cicd-build-publish-artifacts-go@0.4.0
# with:
Comment on lines +153 to +160
# cd-release:
# runs-on: ubuntu-latest
# permissions:
# id-token: write
# contents: read
# steps:
# - name: cd-release
# uses: smartcontractkit/.github/actions/cicd-changesets@01d931b0455a754d12e7143cc54a5a3521a8f6f6 # cicd-changesets@0.3.6
@jkongie jkongie force-pushed the release-please-implementation branch from 88560e0 to 6f9c7a2 Compare May 8, 2026 07:32
@cl-sonarqube-production
Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants