chore(main): release ogis 1.0.0#122
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughBump project versions from 0.2.0 to 1.0.0 across the release manifest, Rust crate, and TypeScript package; add a ChangesRelease bump + Changelog
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This is an automated release PR generated by release-please to publish version 0.3.0 of the ogis (Open Graph Image Service) project. The PR updates version numbers across all package manifests and adds a comprehensive CHANGELOG.md documenting all features and bug fixes introduced since version 0.2.0.
Changes:
- Version bumped from 0.2.0 to 0.3.0 across all package files
- Added CHANGELOG.md documenting 253 feature commits and 21 bug fixes
- Updated release manifest to track the new version
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/typescript/package.json | Updated TypeScript package version to 0.3.0 |
| Cargo.toml | Updated Rust package version to 0.3.0 |
| Cargo.lock | Updated lockfile to reflect new version 0.3.0 |
| CHANGELOG.md | Added comprehensive changelog for version 0.3.0 with all features and fixes since 0.2.0 |
| .release-please-manifest.json | Updated release tracking manifest to version 0.3.0 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
3388d84 to
4bf85c1
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
packages/typescript/package.json (1)
55-55:globalsis one major version behind the current latest.The current latest
globalsrelease is 17.3.0. The declared range^16.5.0caps at<17.0.0, so it will never resolve to v17. v17.0.0 is a breaking change as a few globals were removed, so upgrading needs a quick check against your ESLint config, but staying on v16 indefinitely means missing future environment additions.♻️ Suggested update
- "globals": "^16.5.0", + "globals": "^17.0.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/typescript/package.json` at line 55, Update the "globals" dependency from "^16.5.0" to "^17.3.0" in packages/typescript/package.json and then run lint/tests to surface any breakages; if ESLint or configs fail due to removed globals in v17 (breaking at 17.0.0), adjust your ESLint environment or rules (search for usages of "globals" and entries in your ESLint config) to remove or replace removed globals and re-run CI until green.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Around line 109-111: Create the missing git tag ogis-v0.2.0 that points to the
commit for the 0.2.0 bump (commit ad63aaa1add1ba9f58914ed4b9a2249d2d75bf7c) so
Release Please can compute the correct ranges; add an annotated tag named
ogis-v0.2.0 on that commit and push the tag to the remote so the changelog
sections and future releases reflect the correct commit history.
---
Nitpick comments:
In `@packages/typescript/package.json`:
- Line 55: Update the "globals" dependency from "^16.5.0" to "^17.3.0" in
packages/typescript/package.json and then run lint/tests to surface any
breakages; if ESLint or configs fail due to removed globals in v17 (breaking at
17.0.0), adjust your ESLint environment or rules (search for usages of "globals"
and entries in your ESLint config) to remove or replace removed globals and
re-run CI until green.
| * bump version to 0.1.1 in package.json ([ba77883](https://github.com/twangodev/ogis/commit/ba77883cf55687471f474f65d72a8ed38105fbba)) | ||
| * bump version to 0.1.2 in package.json ([c966994](https://github.com/twangodev/ogis/commit/c96699478cf059961fedc1be7538f6f7efd41a30)) | ||
| * bump version to 0.2.0 for upcoming release ([ad63aaa](https://github.com/twangodev/ogis/commit/ad63aaa1add1ba9f58914ed4b9a2249d2d75bf7c)) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check whether the ogis-v0.2.0 tag exists in the repository
git tag --list | grep -E '^ogis-v0?\.2\.0$'Repository: twangodev/ogis
Length of output: 40
Create the missing ogis-v0.2.0 git tag.
The ogis-v0.2.0 git tag does not exist in the repository. Version-bump commits for 0.1.1, 0.1.2, and 0.2.0 are appearing in the 0.3.0 section of this changelog because Release Please computes the commit range from the previous tag. Without the ogis-v0.2.0 tag, all prior commits are attributed to 0.3.0. This will cause duplicate entries in the next release and inaccurate commit history. Tag the commit corresponding to the 0.2.0 release with ogis-v0.2.0 to correct this.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 109 - 111, Create the missing git tag ogis-v0.2.0
that points to the commit for the 0.2.0 bump (commit
ad63aaa1add1ba9f58914ed4b9a2249d2d75bf7c) so Release Please can compute the
correct ranges; add an annotated tag named ogis-v0.2.0 on that commit and push
the tag to the remote so the changelog sections and future releases reflect the
correct commit history.
4bf85c1 to
95f6bf8
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "name": "ogis", | ||
| "version": "0.2.0", | ||
| "version": "0.3.0", |
There was a problem hiding this comment.
The workspace package version was bumped to 0.3.0, but the root package-lock.json still records this workspace (packages/typescript) as version 0.2.0. This will cause a lockfile/package mismatch (and typically leads to the lockfile being regenerated on install). Regenerate/update package-lock.json so the workspace entry matches 0.3.0.
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "ogis", | |||
There was a problem hiding this comment.
packages/typescript/package.json declares the workspace name as ogis, but the root workspace script uses npm run dev -w @twangodev/ogis (no workspace with that name exists in the repo). This makes the dev:client script unusable. Either rename this package to @twangodev/ogis or update the root script to target -w ogis/the workspace path.
| "name": "ogis", | |
| "name": "@twangodev/ogis", |
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
95f6bf8 to
f763c7a
Compare
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
f763c7a to
dc0ab55
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
CHANGELOG.md (1)
109-111:⚠️ Potential issue | 🟠 MajorRelease history for 0.3.0 still includes pre-0.3 commits.
Lines 109-111 show prior release bump commits, which indicates the release range is still being computed from the wrong previous tag boundary. Please fix/tag the
ogis-v0.2.0boundary and regenerate this section so 0.3.0 only lists post-0.2.0 commits.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 109 - 111, CHANGELOG.md's 0.3.0 section includes commits from before the intended ogis-v0.2.0 boundary; retag the repository to ensure the correct previous release tag (create or move tag ogis-v0.2.0 to the actual v0.2.0 commit), then regenerate the changelog using your release/changelog script so the 0.3.0 section only lists commits after ogis-v0.2.0; check/update references in CHANGELOG.md and any script that computes the range (the tag name ogis-v0.2.0 and the changelog generation step) and re-run the process to produce the corrected section.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 35: The bullet contains redundant phrasing "fish.svg graphic" — update
the text in CHANGELOG.md for the commit referencing
c51bf1b3b39671f567899727614b8da878be4922 to read "add fish.svg file with
placeholder elements and gradients ([c51bf1b](...))" so it matches the
changelog's concise wording style; ensure the replacement preserves the commit
link and surrounding formatting.
---
Duplicate comments:
In `@CHANGELOG.md`:
- Around line 109-111: CHANGELOG.md's 0.3.0 section includes commits from before
the intended ogis-v0.2.0 boundary; retag the repository to ensure the correct
previous release tag (create or move tag ogis-v0.2.0 to the actual v0.2.0
commit), then regenerate the changelog using your release/changelog script so
the 0.3.0 section only lists commits after ogis-v0.2.0; check/update references
in CHANGELOG.md and any script that computes the range (the tag name ogis-v0.2.0
and the changelog generation step) and re-run the process to produce the
corrected section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7defb53f-902c-4c23-afd0-4a0106e65159
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
.release-please-manifest.jsonCHANGELOG.mdCargo.tomlpackages/typescript/package.json
✅ Files skipped from review due to trivial changes (3)
- .release-please-manifest.json
- Cargo.toml
- packages/typescript/package.json
| * add dotenvy support for environment variable management ([a246468](https://github.com/twangodev/ogis/commit/a246468d43373d2bcd466235f1e076cc3adb4c6a)) | ||
| * add dual theme support for syntax highlighting with Shiki ([0d129a9](https://github.com/twangodev/ogis/commit/0d129a9bbb0781ded7794f79921a7e2b538073f0)) | ||
| * add fish template with color configurations and SVG file reference ([987b52e](https://github.com/twangodev/ogis/commit/987b52e9bc6d55aa506502d72bd1133cc331129e)) | ||
| * add fish.svg graphic with placeholder elements and gradients ([c51bf1b](https://github.com/twangodev/ogis/commit/c51bf1b3b39671f567899727614b8da878be4922)) |
There was a problem hiding this comment.
Use cleaner wording: “fish.svg file” (not “fish.svg graphic”).
Line 35 has redundant phrasing and can be simplified for consistency with the rest of the changelog bullets.
🧰 Tools
🪛 LanguageTool
[style] ~35-~35: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “svg”.
Context: ...aa506502d72bd1133cc331129e)) * add fish.svg graphic with placeholder elements and gradients...
(ACRONYM_TAUTOLOGY)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` at line 35, The bullet contains redundant phrasing "fish.svg
graphic" — update the text in CHANGELOG.md for the commit referencing
c51bf1b3b39671f567899727614b8da878be4922 to read "add fish.svg file with
placeholder elements and gradients ([c51bf1b](...))" so it matches the
changelog's concise wording style; ensure the replacement preserves the commit
link and surrounding formatting.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 5 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
dc0ab55 to
a111091
Compare
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
a111091 to
91f46e7
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (2)
CHANGELOG.md (2)
35-35:⚠️ Potential issue | 🟡 MinorUse cleaner wording: "fish.svg file" instead of "fish.svg graphic".
The phrase "fish.svg graphic" is redundant since SVG already stands for "Scalable Vector Graphics."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@CHANGELOG.md` at line 35, Update the CHANGELOG entry that currently reads "add fish.svg graphic with placeholder elements and gradients ([c51bf1b]...)" to use cleaner wording by replacing "fish.svg graphic" with "fish.svg file" so the entry becomes "add fish.svg file with placeholder elements and gradients ([c51bf1b]...)".
109-111:⚠️ Potential issue | 🟠 MajorVersion bump entries appearing in wrong changelog section.
The version bumps for 0.1.1, 0.1.2, and 0.2.0 should not appear in the 0.3.0 changelog section. This is caused by the missing
ogis-v0.2.0git tag, which prevents Release Please from computing the correct commit range. Without the tag, all commits since the last valid tag are included in this release.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@CHANGELOG.md` around lines 109 - 111, The changelog entries for 0.1.1, 0.1.2, and 0.2.0 are incorrectly included in the 0.3.0 section because the git tag ogis-v0.2.0 is missing; recreate the missing tag (git tag -a ogis-v0.2.0 -m "v0.2.0" <commit>) or otherwise add the correct ogis-v0.2.0 tag pointing at the intended commit, then rerun Release Please / regenerate the changelog so the commit range excludes those older bump commits and moves the 0.1.1/0.1.2/0.2.0 entries back into their proper release sections.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@CHANGELOG.md`:
- Line 35: Update the CHANGELOG entry that currently reads "add fish.svg graphic
with placeholder elements and gradients ([c51bf1b]...)" to use cleaner wording
by replacing "fish.svg graphic" with "fish.svg file" so the entry becomes "add
fish.svg file with placeholder elements and gradients ([c51bf1b]...)".
- Around line 109-111: The changelog entries for 0.1.1, 0.1.2, and 0.2.0 are
incorrectly included in the 0.3.0 section because the git tag ogis-v0.2.0 is
missing; recreate the missing tag (git tag -a ogis-v0.2.0 -m "v0.2.0" <commit>)
or otherwise add the correct ogis-v0.2.0 tag pointing at the intended commit,
then rerun Release Please / regenerate the changelog so the commit range
excludes those older bump commits and moves the 0.1.1/0.1.2/0.2.0 entries back
into their proper release sections.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 84bc1ba8-4582-4dca-8907-2faa4386c51b
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
.release-please-manifest.jsonCHANGELOG.mdCargo.tomlpackages/typescript/package.json
✅ Files skipped from review due to trivial changes (3)
- Cargo.toml
- packages/typescript/package.json
- .release-please-manifest.json
| { | ||
| "name": "ogis", | ||
| "version": "0.2.0", | ||
| "version": "0.3.0", | ||
| "type": "module", |
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
2 times, most recently
from
c29cb4b to
4adb8a9
Compare
| { | ||
| "name": "ogis", | ||
| "version": "0.2.0", | ||
| "version": "0.3.0", |
twangodev
changed the title
twangodev
force-pushed
the
release-please--branches--main--components--ogis
branch
from
4adb8a9 to
628b45f
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--ogis
branch
from
628b45f to
0d1a7fc
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--ogis
branch
from
0d1a7fc to
ad2b148
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--ogis
branch
from
ad2b148 to
5cc287f
Compare
🤖 I have created a release beep boop
1.0.0 (2026-05-09)
⚠ BREAKING CHANGES
gradient-arcticno longer resolve. Callers must select a layout, e.g.gradient-arctic-banner,gradient-arctic-centered, etc. URLs using the old names will fall back to the default template.Features
Bug Fixes
This PR was generated with Release Please. See documentation.