Skip to content

chore(main): release 0.2.0#9

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore(main): release 0.2.0#9
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.0 (2026-07-27)

Features

Bug Fixes

  • include maintenance changes in release notes (b069014)
  • make release retries tolerate propagation (#8) (599bac1)
  • publish release before winget validation (#12) (a8cd4d1)
  • use stable publisher API responses (#10) (7d94da9)
  • verify publishers through stable APIs (#11) (041dd9b)

Documentation

  • document publishing operations (#14) (7dfe613)
  • document Release Please commit conventions (b069014)
  • record npm trusted publisher configuration status (#16) (3e26b37)

Build System and Dependencies

  • deps: bump actions/checkout from 4.3.1 to 7.0.0 (#3) (38db7d3)
  • deps: bump actions/download-artifact from 4.3.0 to 8.0.1 (#4) (4ae106c)
  • deps: bump actions/setup-node from 4.4.0 to 7.0.0 (#6) (062338d)
  • deps: bump actions/upload-artifact from 4.6.2 to 7.0.1 (#7) (34e184b)
  • deps: bump googleapis/release-please-action from 8b8fd2cc23b2e18957157a9d923d75aa0c6f6ad5 to 5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 (#5) (336c601)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested a review from jishnuteegala as a code owner July 18, 2026 15:51
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from cda9197 to 3581c91 Compare July 18, 2026 16:31
@github-actions github-actions Bot changed the title chore(main): release 0.1.1 chore(main): release 0.2.0 Jul 18, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from fb4b650 to c3ba8d0 Compare July 18, 2026 19:10
jishnuteegala added a commit that referenced this pull request Jul 27, 2026
Records the completion of step 1 of the npm trusted publishing migration
in PUBLISHING-SETUP.md.

- Update the credential table: all seven packages now have trusted
publishers configured (2026-07-27), with NPM_TOKEN retained only as the
fallback until provenance is verified.
- Add a migration status note under the sequence so the runbook reflects
where we are.
- Make step 3 executable: a concrete npm view loop that checks
dist.attestations.provenance on all seven packages, plus the provenance
badge check.

Merging this is intentionally a releasable docs: commit, so it lands in
the 0.2.0 release PR (#9) and the subsequent release exercises the OIDC
path end to end (steps 2 and 3). NPM_TOKEN stays in place as the safety
net; the cleanup PR (step 5) follows once provenance is confirmed.
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from c3ba8d0 to 0ba3f0a Compare July 27, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants