Skip to content

chore(main): release 0.5.3#38

Merged
nicknisi merged 1 commit into
mainfrom
release-please--branches--main--components--authkit-session
Jun 4, 2026
Merged

chore(main): release 0.5.3#38
nicknisi merged 1 commit into
mainfrom
release-please--branches--main--components--authkit-session

Conversation

@github-actions

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

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.5.3 (2026-06-04)

Bug Fixes

  • rename workflow to release.yml to match npm trusted publisher (42efdca)
  • retry token refresh once on rate limit (#39) (edcfb2a)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--authkit-session branch from 7407893 to 09f81d3 Compare May 18, 2026 15:06
@greptile-apps

greptile-apps Bot commented May 18, 2026

Copy link
Copy Markdown

Greptile Summary

This is an automated release PR generated by Release Please, bumping the package version from 0.5.2 to 0.5.3 across package.json and .release-please-manifest.json, and appending the corresponding changelog entry.

  • package.json: Version field updated from 0.5.20.5.3.
  • .release-please-manifest.json: Manifest updated to reflect the new version.
  • CHANGELOG.md: New 0.5.3 entry added documenting two bug fixes: renaming the release workflow to release.yml and adding retry logic for token refresh on rate-limit errors.

Confidence Score: 5/5

Automated release PR containing only version bumps and a changelog update — no logic, no runtime behavior changed.

All three changed files are purely mechanical: a version string in package.json, the matching entry in .release-please-manifest.json, and the prepended CHANGELOG.md section. None of the actual bug fixes (workflow rename, rate-limit retry) are in this diff; they were already merged. There is nothing here that could introduce a regression.

No files require special attention.

Important Files Changed

Filename Overview
package.json Version bumped from 0.5.2 to 0.5.3; no other changes.
.release-please-manifest.json Manifest version updated from 0.5.2 to 0.5.3 to match the new package version.
CHANGELOG.md New 0.5.3 changelog entry prepended listing two bug fixes from included commits.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|generates| B[Release PR #38]
    B --> C[package.json\nv0.5.2 → v0.5.3]
    B --> D[.release-please-manifest.json\n0.5.2 → 0.5.3]
    B --> E[CHANGELOG.md\nAdd 0.5.3 entry]
    E --> F[Bug Fix: rename workflow to release.yml]
    E --> G[Bug Fix: retry token refresh on rate limit]
    B -->|merge| H[Tag v0.5.3]
    H -->|trigger| I[Publish to npm]
Loading

Reviews (2): Last reviewed commit: "chore(main): release 0.5.3" | Re-trigger Greptile

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--authkit-session branch from 09f81d3 to 91e42d1 Compare June 4, 2026 18:14
@nicknisi nicknisi merged commit 9b09b78 into main Jun 4, 2026
2 checks passed
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant