Skip to content

chore: release v1.6.0#205

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

chore: release v1.6.0#205
JoachimLK wants to merge 1 commit into
mainfrom
release-please--branches--main--components--reqcore

Conversation

@JoachimLK

@JoachimLK JoachimLK commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.6.0 (2026-06-21)

✨ Features

  • add ApplicationBuilderPreview and ApplicationFormBody components for candidate application preview and submission (5118b6e)
  • add end-to-end tests for privacy retention and GDPR compliance flows (a0e2b58)
  • enable GDPR cleanup sweep in E2E tests and validate cleanup response (dd16794)
  • enforce demo account isolation and organization access restrictions (f47296e)
  • enforce demo account isolation and organization access restrictions (72433b9)
  • enhance GDPR retention and erasure processes with improved confirmation and settings (6e110c3)
  • enhance job creation wizard with validation and schema updates; limit questions and criteria (b128764)
  • enhance job question validation and update schemas; add question state validation and tests (18bdd9f)
  • handle organization update and delete errors with proper error handling (989cca3)
  • implement candidate erasure service and GDPR retention logic (8692040)
  • implement candidate erasure service and GDPR retention logic (b2910f8)
  • implement candidate retention and erasure processes (7ee6ee3)
  • jobs: polish job creation wizard (1926a8a)
  • update dialog type for candidate erasure confirmation and refine legal hold handling in delete API (bd2d156)

🐛 Bug Fixes

  • improve log handling in migration and S3 bucket readiness checks (29fa699)
  • refine rate limiting logic for production environment (0d9c219)

♻️ Refactoring

  • remove JobQuestions component to streamline job wizard UI (69ace61)
  • remove unused aiScoringChosen state and update form storage logic; add debug sign-in page script (9b20abd)

🧪 Testing

  • enhance organization delete error handling in auth client tests (d533052)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Added application preview and submission functionality
    • Enhanced job creation wizard with improved validation
    • Implemented GDPR-compliant candidate data management features
  • Bug Fixes

    • Strengthened organization access control and demo-account isolation
    • Improved error handling for organization operations
    • Refined production rate limiting
  • Testing

    • Expanded test coverage for new features and improvements

@railway-app railway-app Bot temporarily deployed to applirank / reqcore-pr-205 June 17, 2026 08:18 Destroyed
@railway-app

railway-app Bot commented Jun 17, 2026

Copy link
Copy Markdown

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

Service Status Web Updated (UTC)
applirank ✅ Success (View Logs) Jun 21, 2026 at 6:56 am

@JoachimLK JoachimLK force-pushed the release-please--branches--main--components--reqcore branch from 2afd22f to 1b675da Compare June 19, 2026 12:08
@railway-app railway-app Bot temporarily deployed to applirank / reqcore-pr-205 June 19, 2026 12:08 Destroyed
@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Version bumped from 1.5.0 to 1.6.0 in package.json and .release-please-manifest.json. CHANGELOG.md gains a new v1.6.0 (2026-06-21) section documenting features, bug fixes, refactoring, and testing entries with linked commit references.

Changes

Release 1.6.0 version bump

Layer / File(s) Summary
Version bump and changelog
package.json, .release-please-manifest.json, CHANGELOG.md
version field updated from 1.5.0 to 1.6.0 in both package.json and .release-please-manifest.json; CHANGELOG.md receives a new v1.6.0 section with categorized entries under Features, Bug Fixes, Refactoring, and Testing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • reqcore-inc/reqcore#72: Same Release Please version bump pattern updating .release-please-manifest.json, package.json, and CHANGELOG.md to a new version.
  • reqcore-inc/reqcore#76: Identical versioning artifact updates across the same three files as this PR.
  • reqcore-inc/reqcore#172: Directly precedes this PR in the Release Please versioning pipeline, bumping the same fields in the same files.

Suggested labels

autorelease: tagged

🐇 A hop, a skip, the version grows,
From five to six the changelog flows,
Features, fixes, refactors bright,
Tagged and sealed — the release takes flight!
🎉 1.6.0, ready to go! 🎉

🚥 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 lacks required sections from the template (Summary, Type of change, Validation, DCO checkboxes), but this is typical for automated release PRs. For automated release PRs, consider if the template requirements should apply differently, or document the expected format for Release Please-generated PRs.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: release v1.6.0' follows Conventional Commits format and accurately summarizes the PR as an automated release of version 1.6.0.
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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Around line 28-29: The CHANGELOG.md file contains duplicate entries for the
same features: lines 28-29 both document "enforce demo account isolation and
organization access restrictions" with different commit hashes, and lines 34-35
both document "implement candidate erasure service and GDPR retention logic"
with different commit hashes. Remove one of each duplicate pair by keeping only
a single entry per feature. Verify which commit hash is correct for each feature
and retain that entry, then delete the duplicate line to consolidate the
changelog.
🪄 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: bde4b04d-f81b-4cd5-a525-5731ad78b50d

📥 Commits

Reviewing files that changed from the base of the PR and between 1b675da and 43ba546.

⛔ 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)
  • .release-please-manifest.json
  • package.json

Comment thread CHANGELOG.md
Comment on lines +28 to +29
* enforce demo account isolation and organization access restrictions ([f47296e](https://github.com/reqcore-inc/reqcore/commit/f47296e91bcc3dad116d25152d8791a7d999c054))
* enforce demo account isolation and organization access restrictions ([72433b9](https://github.com/reqcore-inc/reqcore/commit/72433b9c23bc0a9aaa28c03db36c97e86f01e0cf))

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 duplicate changelog entries.

Lines 28–29 both document "enforce demo account isolation and organization access restrictions" with different commit hashes. Similarly, lines 34–35 both document "implement candidate erasure service and GDPR retention logic" with different commit hashes. These appear to be duplicate entries that should be consolidated. Verify which commit(s) should be retained for each feature.

💡 Suggested fix (remove one of each pair)
 * enforce demo account isolation and organization access restrictions ([f47296e](https://github.com/reqcore-inc/reqcore/commit/f47296e91bcc3dad116d25152d8791a7d999c054))
-* enforce demo account isolation and organization access restrictions ([72433b9](https://github.com/reqcore-inc/reqcore/commit/72433b9c23bc0a9aaa28c03db36c97e86f01e0cf))
 * enhance GDPR retention and erasure processes with improved confirmation and settings ([6e110c3](https://github.com/reqcore-inc/reqcore/commit/6e110c36fe007b131080025a2bb4c3b147091370))

and

 * implement candidate erasure service and GDPR retention logic ([8692040](https://github.com/reqcore-inc/reqcore/commit/869204063470a88b060b03a33f353250545291ac))
-* implement candidate erasure service and GDPR retention logic ([b2910f8](https://github.com/reqcore-inc/reqcore/commit/b2910f8592b8a92936076c494f6710c5c11f7a79))
 * implement candidate retention and erasure processes ([7ee6ee3](https://github.com/reqcore-inc/reqcore/commit/7ee6ee315a1c9293e1777f8f1992b486fbda1085))

Also applies to: 34-35

🤖 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 28 - 29, The CHANGELOG.md file contains duplicate
entries for the same features: lines 28-29 both document "enforce demo account
isolation and organization access restrictions" with different commit hashes,
and lines 34-35 both document "implement candidate erasure service and GDPR
retention logic" with different commit hashes. Remove one of each duplicate pair
by keeping only a single entry per feature. Verify which commit hash is correct
for each feature and retain that entry, then delete the duplicate line to
consolidate the changelog.

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