You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- add Changesets config and scripts for workspace releases
- switch publish automation to `changesets/action` with npm Trusted
Publisher
- document the release flow and add an empty changeset for the migration
## Verification
- `bash -ic 'yarn changeset status'`
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,9 +62,22 @@ Use the Reflag with OpenFeature on the server in Node.js through the Reflag Open
62
62
### Versioning
63
63
64
64
1. Create a new branch locally
65
-
2. Run `yarn run version`
66
-
3. Push and PR
65
+
2. Run `yarn changeset`
66
+
3. Select the packages that changed and the correct bump type
67
+
4. Commit the generated file in `.changeset/`
68
+
5. Push and open a PR
67
69
68
70
### Publishing
69
71
70
-
The [Github Action](.github/workflows/publish.yml) will automatically publish any versioned packages when merging to `main`
72
+
Repository setup:
73
+
74
+
1. Configure npm Trusted Publisher entries for the packages in this repo against the `reflagcom/javascript` GitHub repository and the `publish.yml` workflow
75
+
2. Keep the workflow on GitHub-hosted runners with `id-token: write`, plus `contents: write` and `pull-requests: write` for the release PR flow
76
+
77
+
When a PR with one or more changesets is merged to `main`, the release workflow will open or update a `Version Packages` PR.
0 commit comments