Skip to content

chore: enable dep-cooldown blocking check#160

Open
akshanshjaiswal-atlan wants to merge 4 commits into
mainfrom
chore/enable-dep-cooldown
Open

chore: enable dep-cooldown blocking check#160
akshanshjaiswal-atlan wants to merge 4 commits into
mainfrom
chore/enable-dep-cooldown

Conversation

@akshanshjaiswal-atlan
Copy link
Copy Markdown

Adds the org-shared dep-cooldown CI check to this repo.

What it does

On every PR that modifies (or doesn't) a lockfile, the check runs in <15 seconds. If the PR introduces any dep version published less than 7 days ago, the check fails. Pairs with the org-level branch ruleset (currently in evaluate mode) — once that ruleset goes active for this repo, fresh-dep PRs will be blocked from merging.

Why we're doing this

Manual npm install some-fresh-package and committing the lockfile is a documented attack vector — it bypasses Renovate-style automation gates. Cooldown is the cheapest defense and applies uniformly across npm / pnpm / yarn lockfiles.

What you need to do

  • Nothing for normal flow. The check just runs alongside your existing CI.
  • If a CVE patch needs to fast-track, add the security label to the PR — cooldown is skipped for that PR.

Where the policy lives

Reusable workflow in atlanhq/.github, pinned to a specific SHA in this file. Bumping the SHA is a deliberate review action.

Reference

@github-actions
Copy link
Copy Markdown

We couldn't connect to your Atlan Instance, please make sure to set the valid Atlan Instance URL as ATLAN_INSTANCE_URL as this repository's action secret.

Atlan Instance URL: https://beta-governance.atlan.dev

Make sure your Atlan Instance URL is set in the following format.
https://tenant.atlan.com

Set your repository action secrets here. For more information on how to setup the Atlan dbt Action, please read the setup documentation here.


⚠️ Deprecation Notice: This action is scheduled for deprecation and will no longer be supported after June 2025. To ensure a smooth transition and continued functionality, please migrate to atlan-action by following the migration guide available here.

Some atlanhq repos use master / staging / develop as their default
branch. Hardcoding branches:[main] in the workflow trigger silently
skips those repos. Drop the filter — the check should run on every PR
regardless of base.
Per team decision, accepting the operational simplicity of @main over
SHA pinning. Each upstream change in atlanhq/.github will now
propagate to every consumer instantly. Revisit when ready to adopt
Dependabot for automated SHA bumps.
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