Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/fuzzy-corners-wink.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
2 changes: 2 additions & 0 deletions .changeset/soft-rats-stare.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
6 changes: 3 additions & 3 deletions .github/workflows/changesets.yml
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,12 @@ jobs:
- name: Install package dependencies
run: npm ci

- name: Create Release Pull Request or Publish
- name: Create Release Pull Request
uses: changesets/action@v1
with:
version: npm run changeset:version
publish: npm run changeset:tag
createGithubReleases: true
title: "chore(release): version packages"
title: "chore: release new version 🚀"
commit: "chore: version packages"
Comment thread
cameri marked this conversation as resolved.
env:
GITHUB_TOKEN: ${{ secrets.RELEASE_PAT }}
1 change: 0 additions & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@ name: Release
on:
release:
types: [published]
workflow_dispatch:

jobs:
build-and-push-image:
Expand Down
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -353,8 +353,8 @@ This applies to PRs that exclusively contain:
### Release process

1. Changesets accumulate as PRs are merged to `main`
2. The `Changesets Release` workflow automatically opens a **"Version Packages"** PR that aggregates all pending changesets, bumps `package.json`, and updates `CHANGELOG.md`
3. When a maintainer merges the Version Packages PR, the workflow publishes a GitHub release and creates the corresponding git tag
2. The `Changesets Release` workflow automatically opens a **"chore: release new version 🚀"** PR that aggregates all pending changesets, bumps `package.json`, and updates `CHANGELOG.md`
3. When a maintainer merges the **"chore: release new version 🚀"** PR, the workflow publishes a GitHub release and creates the corresponding git tag
4. The Docker image is then automatically built and pushed to GHCR via the `release.yml` workflow

## Code Quality
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@
"postdocker:integration:run": "docker compose -f ./test/integration/docker-compose.yml down",
"prepare": "husky install || exit 0",
"changeset:version": "changeset version",
"changeset:tag": "changeset tag"
"changeset:publish": "changeset publish"
},
"repository": {
"type": "git",
Expand Down
Loading