Skip to content

Improvements and additions to CHANGELOG.md#71

Merged
aspiers merged 6 commits intomainfrom
changelog-fixes
Apr 11, 2026
Merged

Improvements and additions to CHANGELOG.md#71
aspiers merged 6 commits intomainfrom
changelog-fixes

Conversation

@aspiers
Copy link
Copy Markdown
Contributor

@aspiers aspiers commented Apr 11, 2026

Summary by CodeRabbit

  • Documentation
    • Enforced stricter formatting for changeset summaries and bodies to ensure single-line summary and unwrapped body lines.
    • Updated changelog wording and formatting for consistency across versions.
    • Renamed and clarified sign-in UI reference to “sign-in consent screen.”
    • Added documentation for trusted apps optionally skipping the consent screen on new-user signups.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
epds-demo Ready Ready Preview, Comment Apr 11, 2026 2:48pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 11, 2026

Warning

Rate limit exceeded

@aspiers has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 7 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 26 minutes and 7 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e6358757-dc0d-49a2-b1cd-d4fc3c500f08

📥 Commits

Reviewing files that changed from the base of the PR and between b94bc34 and dd4a173.

📒 Files selected for processing (1)
  • CHANGELOG.md
📝 Walkthrough

Walkthrough

Updated two documentation files: changeset writing guide now enforces single-line summary and unwrapped paragraph body; changelog updated for 0.2.2 with consent-screen wording and a trusted-app consent-skip entry plus revised domain sign-in fix wording.

Changes

Cohort / File(s) Summary
Changeset Writing Guide
.agents/skills/writing-changesets/SKILL.md
Enforced stricter formatting: “Summary sentence” must be one physical line; body prose must be unwrapped with one paragraph per physical line. Condensed instructions and rewrote example changeset lines to be single-line where required.
Release Notes / Changelog
CHANGELOG.md
Updated 0.2.2 notes: changed “sign-in approval screen” to “sign-in consent screen”; added trusted-app opt-in epds_skip_consent_on_signup: true and operator flag PDS_SIGNUP_ALLOW_CONSENT_SKIP=true; rewrote domain sign-in failure entry to describe prior unreleased bug and technical details; reformatted older entries to single-line paragraphs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I nibbled lines and smoothed each seam,

Summary snug, and prose unstream,
Consent named true, changelog set right,
A tidy hop through docs tonight.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Improvements and additions to CHANGELOG.md' is vague and generic, failing to communicate the specific nature of the changes made to the documentation and formatting rules. Consider a more specific title that captures the main intent, such as 'Enforce stricter line formatting in changesets and update release notes' or 'Refactor CHANGELOG formatting and add consent-skip feature documentation'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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 changelog-fixes

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.

@railway-app
Copy link
Copy Markdown

railway-app bot commented Apr 11, 2026

🚅 Deployed to the ePDS-pr-71 environment in ePDS

Service Status Web Updated (UTC)
@certified-app/demo ✅ Success (View Logs) Web Apr 11, 2026 at 2:47 pm
@certified-app/demo untrusted ✅ Success (View Logs) Web Apr 11, 2026 at 2:46 pm
@certified-app/pds-core ✅ Success (View Logs) Web Apr 11, 2026 at 2:46 pm
@certified-app/auth-service ✅ Success (View Logs) Web Apr 11, 2026 at 2:46 pm

@railway-app railway-app bot temporarily deployed to ePDS / ePDS-pr-71 April 11, 2026 14:43 Destroyed
@coveralls-official
Copy link
Copy Markdown

coveralls-official bot commented Apr 11, 2026

Coverage Report for CI Build 24284853328

Coverage remained the same at 31.705%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 1671
Covered Lines: 554
Line Coverage: 33.15%
Relevant Branches: 950
Covered Branches: 277
Branch Coverage: 29.16%
Branches in Coverage %: Yes
Coverage Strength: 2.79 hits per line

💛 - Coveralls

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: 2

🤖 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 39: In the CHANGELOG entry sentence that currently reads "This is just a
heads up in case anyone deployed...", replace the unhyphenated phrase "heads up"
with the hyphenated form "heads-up" so the sentence becomes "This is just a
heads-up in case anyone deployed..."; update only that token in the line
referencing v0.2.2 and keep the rest of the sentence unchanged.
- Line 53: Update the CHANGELOG entry that currently reads “PR
[`#21`](https://github.com/hypercerts-org/ePDS/issues/21)” to point to the pull
request URL by replacing `/issues/21` with `/pull/21` and ensure the visible
text stays “PR `#21`”; edit the line containing the double-redirect description
(the string "PR `#21`" and its markdown link) so the link target is
https://github.com/hypercerts-org/ePDS/pull/21.
🪄 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: c903beb4-4674-475e-8368-f3cc81c19ec5

📥 Commits

Reviewing files that changed from the base of the PR and between 2b4180e and 156fcdb.

📒 Files selected for processing (2)
  • .agents/skills/writing-changesets/SKILL.md
  • CHANGELOG.md

Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
aspiers added 3 commits April 11, 2026 15:47
Make it clear this was not an issue with a released version and
only broken in git for a small time window.
@sonarqubecloud
Copy link
Copy Markdown

@aspiers aspiers merged commit 2fd9925 into main Apr 11, 2026
14 checks passed
@aspiers aspiers deleted the changelog-fixes branch April 11, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant