Add documentation for automating changesets when versioning apps#1905
Add documentation for automating changesets when versioning apps#1905ThisIsMissEm wants to merge 1 commit intochangesets:mainfrom
Conversation
…non-npm projects) I just used changesets for versioning a swift package, with the GitHub Action and the GitHub changelog setup, and I was stuck for a moment where the release pull request would be created, but merging it would result in the log output: ``` Run changesets/action@v1 setting git user /usr/bin/git config user.name "github-actions[bot]" /usr/bin/git config user.email "<omitted>" setting GitHub credentials No changesets found. Attempting to publish any unpublished packages to npm No NPM_TOKEN found, but OIDC is available - using npm trusted publishing ``` And then no github release was actually created. This was because I didn't supply the `publish` option to the GitHub Action, which needs to invoke `changeset publish` You can see the final configuration I'm using for publishing releases of swift packages here: https://github.com/germ-network/oauth4swift
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1905 +/- ##
=======================================
Coverage 84.24% 84.24%
=======================================
Files 56 56
Lines 2419 2419
Branches 729 728 -1
=======================================
Hits 2038 2038
Misses 375 375
Partials 6 6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I'm not sure if this documentation change needs a changeset or not in this project? |
1 participant
(or for non-npm projects)
I just used changesets for versioning a swift package, with the GitHub Action and the GitHub changelog setup, and I was stuck for a moment where the release pull request would be created, but merging it would result in the following log output:
And then no github release was actually created.
This was because I didn't supply the
publishoption to the GitHub Action, which needs to invokechangeset publish, because I was like "I don't have a publish command for swift, since there's no package registry", so I'd both omitted it initially, and then setpublish: /usr/bin/trueand both didn't have the expected results.You can see the final configuration I'm using for publishing releases of swift packages here: https://github.com/germ-network/oauth4swift