Skip to content

chore: release v1.5.0#172

Open
JoachimLK wants to merge 1 commit intomainfrom
release-please--branches--main--components--reqcore
Open

chore: release v1.5.0#172
JoachimLK wants to merge 1 commit intomainfrom
release-please--branches--main--components--reqcore

Conversation

@JoachimLK
Copy link
Copy Markdown
Contributor

@JoachimLK JoachimLK commented May 3, 2026

🤖 I have created a release beep boop

1.5.0 (2026-05-04)

✨ Features

  • add pgDumpEnv utility to secure environment variable handling (6fe4900)
  • enhance color mode functionality and improve UI responsiveness (8068e4e)
  • implement nonce-based CSP middleware for enhanced security (bfb4483)
  • implement nonce-based CSP middleware for enhanced security (6fe4900)

🐛 Bug Fixes

  • enhance rate limiting logic and add tests (6fe4900)
  • update comments for clarity and enhance rate limiting logic in production (921ea39)

🧪 Testing

  • add security tests for recent fixes (6fe4900)
  • add unit tests for pgDumpEnv utility (6fe4900)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

v1.5.0 Release

  • New Features

    • Added pgDumpEnv environment handling
    • Improved color mode support
    • Enhanced UI responsiveness
    • Added nonce-based CSP middleware
  • Bug Fixes

    • Improved rate limiting logic
  • Tests

    • Added security tests
    • Added pgDumpEnv unit tests

@railway-app
Copy link
Copy Markdown

railway-app Bot commented May 3, 2026

🚅 Deployed to the reqcore-pr-172 environment in applirank

Service Status Web Updated (UTC)
applirank ✅ Success (View Logs) May 4, 2026 at 9:16 am

@railway-app railway-app Bot temporarily deployed to applirank / reqcore-pr-172 May 3, 2026 12:07 Destroyed
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 3, 2026

📝 Walkthrough

Walkthrough

This PR bumps the project version from 1.4.0 to 1.5.0 and updates release metadata and changelog entries: .release-please-manifest.json and package.json versions are incremented and CHANGELOG.md gains a v1.5.0 section listing features, bug fixes, and tests.

Changes

Version Bump & Release Notes

Layer / File(s) Summary
Version Metadata
.release-please-manifest.json, package.json
Root package version for "." changed from 1.4.0 to 1.5.0.
Release Notes
CHANGELOG.md
Added v1.5.0 (2026-05-04) section under ## Unreleased with bullets for Features (pgDumpEnv, color mode/UI responsiveness, nonce-based CSP middleware), Bug Fixes (rate limiting logic), and Testing (security and unit tests).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

autorelease: tagged

Poem

🐰 A little hop from one to the next,
1.4.0 to 1.5.0, tidy and text.
Changelog leaves a trail of new light,
Manifest nods, package dressed right.
Hooray — a rabbit cheers the release tonight!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description is auto-generated by Release Please and contains release notes rather than following the template's Summary and Type of change sections. Consider whether auto-generated Release Please PRs should follow the manual template, or if release automation PRs have their own expected format.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'chore: release v1.5.0' follows Conventional Commits format and clearly identifies the main change—a version release.
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.

✏️ 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--components--reqcore

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
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

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 25-26: The CHANGELOG contains a duplicate entry for "implement
nonce-based CSP middleware for enhanced security" (shown with commits bfb4483
and 6fe4900); edit CHANGELOG.md to remove the redundant line so the 1.5.0 notes
list this feature only once (or, if the commits represent distinct changes,
replace one entry with a clarified/differentiated description referencing the
appropriate commit hash).
🪄 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: ffbce87e-3880-4cb4-b082-1b10072523c6

📥 Commits

Reviewing files that changed from the base of the PR and between bfb4483 and e6fbad3.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json

Comment thread CHANGELOG.md
Comment on lines +25 to +26
* implement nonce-based CSP middleware for enhanced security ([bfb4483](https://github.com/reqcore-inc/reqcore/commit/bfb44830d3205dc9e8c5392fdabdb8da4ed37a5e))
* implement nonce-based CSP middleware for enhanced security ([6fe4900](https://github.com/reqcore-inc/reqcore/commit/6fe490000487779ad008277ee650ded375bdbcf9))
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicated feature entry in the 1.5.0 notes.

CHANGELOG.md Line 25 and Line 26 describe the same nonce-based CSP middleware feature, which makes the release notes misleading/redundant. Keep only one entry (or differentiate if they are actually distinct changes).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 25 - 26, The CHANGELOG contains a duplicate entry
for "implement nonce-based CSP middleware for enhanced security" (shown with
commits bfb4483 and 6fe4900); edit CHANGELOG.md to remove the redundant line so
the 1.5.0 notes list this feature only once (or, if the commits represent
distinct changes, replace one entry with a clarified/differentiated description
referencing the appropriate commit hash).

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
CHANGELOG.md (1)

25-26: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove the duplicated “nonce-based CSP middleware” entry.

Lines 25 and 26 contain the exact same feature description; this makes the release notes redundant/misleading. Either keep only one bullet or merge them into a single line (or differentiate the text if they truly represent distinct changes).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 25 - 26, Remove the duplicate changelog entry for
"implement nonce-based CSP middleware for enhanced security" by keeping only one
bullet that references the two commits (bfb4483 and 6fe4900) or by merging them
into a single line that lists both commit hashes; update the single bullet to
include both commits or remove the redundant line so only one occurrence of the
phrase "implement nonce-based CSP middleware for enhanced security" remains.
🤖 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: Update the two changelog entries containing the phrase
"rate limiting" to use the hyphenated compound adjective "rate-limiting" (i.e.,
change "enhance rate limiting logic and add tests" and "enhance rate limiting
logic in production" to "enhance rate-limiting logic and add tests" and "enhance
rate-limiting logic in production"); ensure both commits referenced in the two
bullets are edited so the changelog consistently uses "rate-limiting".

---

Duplicate comments:
In `@CHANGELOG.md`:
- Around line 25-26: Remove the duplicate changelog entry for "implement
nonce-based CSP middleware for enhanced security" by keeping only one bullet
that references the two commits (bfb4483 and 6fe4900) or by merging them into a
single line that lists both commit hashes; update the single bullet to include
both commits or remove the redundant line so only one occurrence of the phrase
"implement nonce-based CSP middleware for enhanced security" remains.
🪄 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: c453ce9c-3492-4113-af3f-19b49cea0d7a

📥 Commits

Reviewing files that changed from the base of the PR and between e6fbad3 and 516e353.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json
✅ Files skipped from review due to trivial changes (2)
  • package.json
  • .release-please-manifest.json

Comment thread CHANGELOG.md
Comment on lines +31 to +32
* enhance rate limiting logic and add tests ([6fe4900](https://github.com/reqcore-inc/reqcore/commit/6fe490000487779ad008277ee650ded375bdbcf9))
* update comments for clarity and enhance rate limiting logic in production ([921ea39](https://github.com/reqcore-inc/reqcore/commit/921ea399bc35fbb006274d98faf7433fedf88aa5))
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Hyphenate “rate-limiting” (compound adjective).

Static analysis suggests the changelog phrasing “rate limiting” should be “rate-limiting” as a compound adjective. Consider updating Lines 31-32 accordingly for consistency and correctness.

As per coding guidelines, “If applicable, propose fixes … without fixing an immediate user-visible problem.” This is a low-risk documentation polish backed by static analysis hints.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~31-~31: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...5bdbcf9)) ### 🐛 Bug Fixes * enhance rate limiting logic and add tests ([6fe4900](https://...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~32-~32: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...update comments for clarity and enhance rate limiting logic in production ([921ea39](https://...

(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 31 - 32, Update the two changelog entries
containing the phrase "rate limiting" to use the hyphenated compound adjective
"rate-limiting" (i.e., change "enhance rate limiting logic and add tests" and
"enhance rate limiting logic in production" to "enhance rate-limiting logic and
add tests" and "enhance rate-limiting logic in production"); ensure both commits
referenced in the two bullets are edited so the changelog consistently uses
"rate-limiting".

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