Skip to content

chore: bump min release age to 7 days for pnpm packages#6789

Merged
LesnyRumcajs merged 1 commit intomainfrom
increase-pnpm-min-release-age
Mar 25, 2026
Merged

chore: bump min release age to 7 days for pnpm packages#6789
LesnyRumcajs merged 1 commit intomainfrom
increase-pnpm-min-release-age

Conversation

@LesnyRumcajs
Copy link
Copy Markdown
Member

@LesnyRumcajs LesnyRumcajs commented Mar 25, 2026

Summary of changes

Changes introduced in this pull request:

  • 1 day is a bit low; not a huge deal for us, but given most such configs are copy-pasted, let's stick to good practices.

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

  • I have performed a self-review of my own code,
  • I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
  • I have added tests that prove my fix is effective or that my feature works (if possible),
  • I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

  • I have read and agree to the CONTRIBUTING document.
  • I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

  • Chores
    • Updated supply-chain security configuration to enforce a longer stability period for dependencies before release.

@LesnyRumcajs LesnyRumcajs requested a review from a team as a code owner March 25, 2026 07:50
@LesnyRumcajs LesnyRumcajs requested review from akaladarshi and sudo-shashank and removed request for a team March 25, 2026 07:50
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b3eb8609-47cc-470a-9837-2fd2caa71de0

📥 Commits

Reviewing files that changed from the base of the PR and between 7868455 and b0d63b3.

📒 Files selected for processing (1)
  • docs/pnpm-workspace.yaml

Walkthrough

Updated the pnpm supply-chain security configuration by increasing minimumReleaseAge from 1440 to 10080 minutes (7 days) in the workspace configuration file with an inline comment clarifying the duration.

Changes

Cohort / File(s) Summary
Supply-chain Security Configuration
docs/pnpm-workspace.yaml
Updated minimumReleaseAge parameter from 1440 to 10080 minutes (7 days) with clarifying inline comment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

dependencies

Suggested reviewers

  • akaladarshi
  • sudo-shashank
  • hanabi1224
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title directly and clearly summarizes the main change: updating the minimum release age for pnpm packages from 1 day to 7 days, which is the sole focus of the changeset.
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 increase-pnpm-min-release-age
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch increase-pnpm-min-release-age

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

@LesnyRumcajs LesnyRumcajs added this pull request to the merge queue Mar 25, 2026
Merged via the queue into main with commit b0139fe Mar 25, 2026
11 checks passed
@LesnyRumcajs LesnyRumcajs deleted the increase-pnpm-min-release-age branch March 25, 2026 08:21
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.

2 participants