chore: release v1.1.0#72
Merged
JoachimLK merged 1 commit intoMar 10, 2026
Merged
Conversation
|
🚅 Deployed to the reqcore-pr-72 environment in applirank
|
📝 WalkthroughWalkthroughThis PR updates the project release to 1.1.0: bumps versions in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
CHANGELOG.md (1)
9-22: Avoid mixing versioned and date-based changelog formats.This new Release Please block switches to
[version] + Features/Bug Fixes, but the file still documents changes by date withAdded/Changed/Fixed/Removedright below, so the March 8 release is now effectively represented twice. I’d pick one format and make the generated entry match it to keep the changelog single-source.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 9 - 22, The changelog now mixes a versioned release block ("## [1.1.0] (2026-03-08)" with "### ✨ Features" / "### 🐛 Bug Fixes") and the project’s older date-based (Added/Changed/Fixed/Removed) sections; pick one format and make the new entry match it consistently. For example, if you keep the versioned format, remove or merge the subsequent date-based "Added/Changed/Fixed/Removed" lines into the "## [1.1.0]" block (consolidating entries under "### ✨ Features" and "### 🐛 Bug Fixes"); alternatively, convert the new release-please block to the existing date-based style and delete the "## [1.1.0]" header. Update the file so only one style appears and ensure entries (commit summaries like the ones under "### ✨ Features") are moved into the chosen format.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@CHANGELOG.md`:
- Around line 9-22: The changelog now mixes a versioned release block ("##
[1.1.0] (2026-03-08)" with "### ✨ Features" / "### 🐛 Bug Fixes") and the
project’s older date-based (Added/Changed/Fixed/Removed) sections; pick one
format and make the new entry match it consistently. For example, if you keep
the versioned format, remove or merge the subsequent date-based
"Added/Changed/Fixed/Removed" lines into the "## [1.1.0]" block (consolidating
entries under "### ✨ Features" and "### 🐛 Bug Fixes"); alternatively, convert
the new release-please block to the existing date-based style and delete the "##
[1.1.0]" header. Update the file so only one style appears and ensure entries
(commit summaries like the ones under "### ✨ Features") are moved into the
chosen format.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1a5fc1db-bd7a-4adf-8c67-53101a02f8e0
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.release-please-manifest.jsonCHANGELOG.mdpackage.json
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
dc13b46 to
47e7658
Compare
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 9: Update the release date for version 1.1.0 in the changelog: locate the
header string "##
[1.1.0](https://github.com/reqcore-inc/reqcore/compare/v1.0.0...v1.1.0)
(2026-03-09)" and change the date to 2026-03-08 so the changelog entry matches
the PR metadata.
- Around line 17-18: The two CHANGELOG bullets for PostHog are duplicates;
either remove one or update each to describe the specific change introduced by
its commit (include the commit hash as reference). Edit the two lines that
mention "integrate PostHog for user analytics and consent management" (the
entries with hashes 8bd4bd5 and 619f239) so they are unique: if both commits
should remain, replace one or both descriptions with concise notes of what each
commit actually changed (e.g., "add PostHog config and opt-in UI" vs "wire
PostHog events for page views"), otherwise delete the redundant line.
- Around line 12-35: The changelog header claims "Keep a Changelog" categories
but the release uses "✨ Features" and "🐛 Bug Fixes"; update the file so the
header and section names match: either change the header text that mentions Keep
a Changelog categories to reflect the current headings ("Features" and "Bug
Fixes") or rename the sections "### ✨ Features" and "### 🐛 Bug Fixes" to the
Keep a Changelog canonical names ("### Added", "### Changed", "### Fixed",
etc.); edit the visible header line and the section headings in CHANGELOG.md
(the lines containing "### ✨ Features" and "### 🐛 Bug Fixes") so the format is
consistent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a3ee0a36-bce1-4553-869f-9ae685646870
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.release-please-manifest.jsonCHANGELOG.mdpackage.json
✅ Files skipped from review due to trivial changes (1)
- .release-please-manifest.json
🚧 Files skipped from review as they are similar to previous changes (1)
- package.json
|
|
||
| --- | ||
|
|
||
| ## [1.1.0](https://github.com/reqcore-inc/reqcore/compare/v1.0.0...v1.1.0) (2026-03-09) |
There was a problem hiding this comment.
Correct the release date for 1.1.0.
Line 9 says 2026-03-09, but the PR metadata describes this release as v1.1.0 (2026-03-08). The changelog date should match the actual release date to avoid conflicting release records.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` at line 9, Update the release date for version 1.1.0 in the
changelog: locate the header string "##
[1.1.0](https://github.com/reqcore-inc/reqcore/compare/v1.0.0...v1.1.0)
(2026-03-09)" and change the date to 2026-03-08 so the changelog entry matches
the PR metadata.
Comment on lines
+12
to
+35
| ### ✨ Features | ||
|
|
||
| * add new article on best free ATS software for startups and update related content ([021f8db](https://github.com/reqcore-inc/reqcore/commit/021f8db2351260cd5e2ac738aa571da85e91f4dc)) | ||
| * add new article on the differences between open source and free ATS, including a comprehensive guide and internal links ([da31e77](https://github.com/reqcore-inc/reqcore/commit/da31e77ba6187f7c8faa6ddb1d626c1fdfe57d82)) | ||
| * add release automation configuration and update versioning ([a37c1cc](https://github.com/reqcore-inc/reqcore/commit/a37c1cc8f032816ab10a184ad3b487d65b5997a7)) | ||
| * **analytics:** integrate PostHog for user analytics and consent management ([8bd4bd5](https://github.com/reqcore-inc/reqcore/commit/8bd4bd50cb62254e9d39f8c92214c2af24b8671c)) | ||
| * **analytics:** integrate PostHog for user analytics and consent management ([619f239](https://github.com/reqcore-inc/reqcore/commit/619f239c06a865a2d1a091a1d5f85a941548b5a7)) | ||
| * **consent:** implement consent banner for analytics tracking and update privacy policy ([24a9201](https://github.com/reqcore-inc/reqcore/commit/24a920163ecf9a3a9a65d4476f115dd34357a34b)) | ||
| * **consent:** simplify consent message for clarity in analytics tracking ([c28356a](https://github.com/reqcore-inc/reqcore/commit/c28356a27eea15715e686cd83686ac7cdb6bd29b)) | ||
| * **consent:** update wording in consent banner for improved clarity ([91c6550](https://github.com/reqcore-inc/reqcore/commit/91c655032d8e3cf515b065b9fe13e216f460c90d)) | ||
| * **database:** enhance database URL resolution with fallback handling for environment variables ([0302102](https://github.com/reqcore-inc/reqcore/commit/0302102c984b04642cd2e4de2bbb4cdcdf88b185)) | ||
| * **dependencies:** update PostHog CLI and related packages for improved functionality ([f532a3e](https://github.com/reqcore-inc/reqcore/commit/f532a3e3c53d522b1d11c93314cf91252400a6f3)) | ||
| * **navbar:** replace static navbar with reusable PublicNavBar component across blog, catalog, docs, and roadmap pages ([a0d17db](https://github.com/reqcore-inc/reqcore/commit/a0d17dbcfe3613d2f5817f54ee9b46758a350ad5)) | ||
| * **nuxt:** conditionally load PostHog module based on API key availability to prevent crashes ([ddb1f59](https://github.com/reqcore-inc/reqcore/commit/ddb1f599ea56b4d938cb8c50b754fac4561070fd)) | ||
| * **posthog:** add PostHog configuration for server-side event capture ([9958fe5](https://github.com/reqcore-inc/reqcore/commit/9958fe5d37ea75366216bcbd5a2187346c62c938)) | ||
| * **posthog:** enhance analytics consent management and data minimization in PostHog integration ([92588d9](https://github.com/reqcore-inc/reqcore/commit/92588d9a3a3801eea7e63bae46d773a9e2dc771c)) | ||
| * **posthog:** enhance PostHog integration with consent handling and graceful shutdown ([5e708fa](https://github.com/reqcore-inc/reqcore/commit/5e708faf1b3808fc24f4a6c51285eb9a4920004b)) | ||
| * **posthog:** replicate safe accessor for PostHog in composables and plugins to ensure compatibility when not configured ([1e948cb](https://github.com/reqcore-inc/reqcore/commit/1e948cbc2e9543e54756f553327454e70c726702)) | ||
|
|
||
|
|
||
| ### 🐛 Bug Fixes | ||
|
|
||
| * add config and manifest file parameters to release-please action ([ff30b11](https://github.com/reqcore-inc/reqcore/commit/ff30b11bbcaea0d7ab92be887e008edc656ba5cc)) | ||
| * update token in release-please action for proper authentication ([5ae917e](https://github.com/reqcore-inc/reqcore/commit/5ae917e3c30cd5e819a1be97045e4890d4ac0f7b)) |
There was a problem hiding this comment.
Align this entry with the changelog format declared above.
Line 5 says this file uses Keep a Changelog categories (Added, Changed, Fixed, Removed), but this release switches to Features and Bug Fixes. Either rename these sections or update the file header so the format is consistent.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~15-~15: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... new article on the differences between open source and free ATS, including a comprehensive...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 12 - 35, The changelog header claims "Keep a
Changelog" categories but the release uses "✨ Features" and "🐛 Bug Fixes";
update the file so the header and section names match: either change the header
text that mentions Keep a Changelog categories to reflect the current headings
("Features" and "Bug Fixes") or rename the sections "### ✨ Features" and "### 🐛
Bug Fixes" to the Keep a Changelog canonical names ("### Added", "### Changed",
"### Fixed", etc.); edit the visible header line and the section headings in
CHANGELOG.md (the lines containing "### ✨ Features" and "### 🐛 Bug Fixes") so
the format is consistent.
Comment on lines
+17
to
+18
| * **analytics:** integrate PostHog for user analytics and consent management ([8bd4bd5](https://github.com/reqcore-inc/reqcore/commit/8bd4bd50cb62254e9d39f8c92214c2af24b8671c)) | ||
| * **analytics:** integrate PostHog for user analytics and consent management ([619f239](https://github.com/reqcore-inc/reqcore/commit/619f239c06a865a2d1a091a1d5f85a941548b5a7)) |
There was a problem hiding this comment.
Deduplicate or differentiate the PostHog entries.
These two bullets read identically and only differ by commit hash. If both commits are meant to appear, the descriptions should explain what changed in each; otherwise one of them should be removed.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 17 - 18, The two CHANGELOG bullets for PostHog are
duplicates; either remove one or update each to describe the specific change
introduced by its commit (include the commit hash as reference). Edit the two
lines that mention "integrate PostHog for user analytics and consent management"
(the entries with hashes 8bd4bd5 and 619f239) so they are unique: if both
commits should remain, replace one or both descriptions with concise notes of
what each commit actually changed (e.g., "add PostHog config and opt-in UI" vs
"wire PostHog events for page views"), otherwise delete the redundant line.
47e7658 to
efcc6b2
Compare
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
efcc6b2 to
6780369
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 31-32: The two identical CHANGELOG.md bullets for PostHog (commits
4b745ec and 4c11f99) should be resolved: either collapse them into a single
combined bullet that mentions both commit hashes and summarizes the net change,
or edit each bullet so they describe their distinct scope (e.g., specify which
env vars or consent handling tweaks were introduced in commit 4b745ec versus
4c11f99); update the lines containing the two PostHog entries so the reader can
tell what each commit changed.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: eab67109-6814-4f3a-a76d-38551957d08e
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.release-please-manifest.jsonCHANGELOG.mdpackage.json
🚧 Files skipped from review as they are similar to previous changes (1)
- .release-please-manifest.json
Comment on lines
+31
to
+32
| * **posthog:** update PostHog integration with environment variables and consent handling ([4b745ec](https://github.com/reqcore-inc/reqcore/commit/4b745ec2f9e768ad11e113799d3b63e17a6cef60)) | ||
| * **posthog:** update PostHog integration with environment variables and consent handling ([4c11f99](https://github.com/reqcore-inc/reqcore/commit/4c11f99c9bc1331989c80b78bf793dd63ec2584f)) |
There was a problem hiding this comment.
Differentiate the two PostHog env-var bullets.
These entries are identical, so readers cannot tell what changed in 4b745ec versus 4c11f99. Please collapse them into one item or give each bullet its specific scope.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 31 - 32, The two identical CHANGELOG.md bullets
for PostHog (commits 4b745ec and 4c11f99) should be resolved: either collapse
them into a single combined bullet that mentions both commit hashes and
summarizes the net change, or edit each bullet so they describe their distinct
scope (e.g., specify which env vars or consent handling tweaks were introduced
in commit 4b745ec versus 4c11f99); update the lines containing the two PostHog
entries so the reader can tell what each commit changed.
Contributor
Author
|
🤖 Created releases: 🌻 |
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
1.1.0 (2026-03-10)
✨ Features
🐛 Bug Fixes
This PR was generated with Release Please. See documentation.