Skip to content

chore: release main#63

Open
jbdevprimary wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore: release main#63
jbdevprimary wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@jbdevprimary
Copy link
Copy Markdown
Contributor

@jbdevprimary jbdevprimary commented May 29, 2026

🤖 I have created a release beep boop

declarative-hex-worlds: 1.0.1

1.0.1 (2026-05-29)

Bug Fixes

  • CR-P0 critical blockers — peer deps, release pin, readJson safety, coverage CI (#62) (038d850)
  • security,ci: CR-P0-4 bootstrap security tests + CR-P1-3/7/8/9/10 hardening batch (#64) (dcfba17)

Performance

  • gameboard/systems: eliminate query spreads + Map default-arg allocations (CR-P2-2, CR-P2-3) (#69) (c416c09)
  • koota+catalog: O(1) entity lookup + isKnownExtraAssetId set (CR-P1-4, CR-P1-5) (#67) (7a6c2a5)
  • pathfinding: O(log N) binary min-heap A* + Dijkstra (CR-P1-1) (#65) (f12210c)

Refactoring

  • cli: decompose _shared.ts into per-command files (CR-P2-1) (#68) (86444aa)
  • guides: invert simple-rpg guide production→test import (CR-P1-2) (#66) (1340074)

This PR was generated with Release Please. See documentation.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 29, 2026

Warning

Review limit reached

@jbdevprimary, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 59 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 06b36590-292b-4622-82f6-c76a977e228c

📥 Commits

Reviewing files that changed from the base of the PR and between 7293df3 and 71012d3.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json
📝 Walkthrough

Walkthrough

This PR releases version 1.0.1 by updating the release-please manifest, package version, and changelog with categorized release notes documenting bug fixes, performance optimizations, and refactoring improvements. A minor comment formatting adjustment is also made in package.json.

Changes

Release v1.0.1

Layer / File(s) Summary
Version bump and release notes
.release-please-manifest.json, package.json, CHANGELOG.md
Release manifest and package version incremented to 1.0.1, with changelog entry documenting bug fixes, performance improvements, and refactoring across the release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • jbcom/declarative-hex-worlds#6: Both PRs are release-bump updates that modify the same versioning artifacts (notably .release-please-manifest.json, package.json, and CHANGELOG.md) to increment the package/changelog from 0.1.01.0.0 vs 1.0.01.0.1.

Suggested labels

autorelease: tagged

Poem

🐰 A version bump hops through the files,
From one-point-oh to one-point-one with smiles,
The changelog sings of fixes and speed,
A tidy release is all that we need!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: release main' clearly and accurately summarizes the PR's primary purpose: creating a release version 1.0.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 29, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request bumps the project version from 1.0.0 to 1.0.1 across the release manifest and package.json, updates the CHANGELOG.md to document the bug fixes in this release, and replaces a unicode escape sequence with an em dash in a package.json comment. There are no review comments, and I have no feedback to provide.

Copy link
Copy Markdown

@amazon-q-developer amazon-q-developer Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a clean automated release PR from release-please that bumps the version from 1.0.0 to 1.0.1. The changes are consistent across all files and correctly reference the bug fixes from PR #62. No blocking issues found.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

@jbdevprimary jbdevprimary force-pushed the release-please--branches--main branch 5 times, most recently from 3acde0c to 69aca6e Compare May 29, 2026 07:55
@jbdevprimary jbdevprimary force-pushed the release-please--branches--main branch from 69aca6e to 71012d3 Compare May 29, 2026 08:12
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.

1 participant