📖 Document new package steps for developers and add changeset validation to PRs#2734
📖 Document new package steps for developers and add changeset validation to PRs#2734rowanc1 merged 7 commits intojupyter-book:mainfrom
Conversation
|
|
| 2. **Set the version to `0.0.0`** in the package's `package.json`. Changesets will overwrite this on the first automated release. | ||
| 3. **Publish the package** manually with public access: | ||
| ```shell | ||
| npm publish --access=public |
There was a problem hiding this comment.
There's no token or anything needed for this step?
There was a problem hiding this comment.
You will need to be logged in, yes.
| npm publish --access=public | ||
| ``` | ||
| 4. **Set up trusted publishing** in the NPM admin so that GitHub Actions can publish future releases automatically. | ||
| 5. **Add `ebp-bot` as a maintainer** on the NPM package page. This is not needed if the package belongs to a team (e.g., `@myst-theme`). |
There was a problem hiding this comment.
What does this statement mean?
Co-authored-by: Stefan van der Walt <stefan@mentat.za.net>
|
Updated based on @stefanv's feedback. Thanks @choldgraf. |
rowanc1
changed the title
3 participants
Two quick things:
npx changesettest to our CI so that malformed changesets would breakI added a bad changeset to see if this fails