You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Record DEPENDABOT_MERGE_TOKEN's expiry in the renewal calendar - #356
Adds a credential-dependabot-merge-pat entry to fleet-reports/lock-in/renewals.yml, so the renewal calendar opens an issue 14 days before the Dependabot sweeper's token lapses.
The token is the fine-grained PAT that ADR-0016 Decision 3 describes. The maintainer minted it and stored it in the main-only dependabot-merge environment at 2026-11-18T02:27Z, with a 366-day expiry: 2027-11-19. The entry follows the existing credential-fleet-reports-pat entry: its name, its category, the date, and a note on how to rotate it. It carries no value or account identifier, as the file's header requires.
Checks
python3 ci/validate.py passes, and the file parses as YAML with both credential entries present.
Review: PR #356, renewal entry for DEPENDABOT_MERGE_TOKEN
minor: fleet-reports/lock-in/renewals.yml:83-94. The entry names the secret DEPENDABOT_MERGE_TOKEN, and its note says the sweeper "fails fast at its token check." Nothing in this checkout references that secret name or a sweeper workflow yet (grep finds only terraform/locals.tf and ADR-0016). ADR-0016's order of work puts the sweeper after this record. The secret name and the failure behaviour can't be confirmed from the diff, so they should match the sweeper once it lands.
minor: fleet-reports/lock-in/renewals.yml:80. next_due: 2027-11-19 is the only record of the token's expiry, and the diff can't check it against the token. A one-day error moves the alarm by one day, so it's worth confirming against the expiry shown in GitHub's token settings. The 366-day lifetime also sits at the edge of ADR-0016 Decision 3's "at most one year."
Checks against the requested focus areas:
The change is a single 14-line addition to one YAML file. It touches no Terraform, workflow, generated artifact, or brand asset.
The entry has no credential values or account identifiers. The note says the value is not in the file, which fits the file's public-repo rules.
The entry's fields match the schema in the file header, and category: credential is an existing value.
Fleet PR-workflow checks: the body has Closes #355, the title matches the change, the scope is one entry, and the summary covers what, why, and the constraints. The 🤖 Generated with Claude Code attribution is present.
Not verified: I could not run ci/validate.py or parse the YAML, because those commands were blocked for approval in this session. The PR body says both pass, and I have not confirmed it.
The date can't be checked against the token, and 366 days sits at the edge of "at most one year".No change. The maintainer stored the token at 2026-11-18T02:27Z with a 366-day expiry, and the date was relayed as 2027-11-19. The 14-day lead absorbs a one-day error. A 366-day expiry is what "at most one year" means in ADR-0016, and the date sits in this file so the calendar warns ahead of it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #355. Part of #346.
Summary
Adds a
credential-dependabot-merge-patentry tofleet-reports/lock-in/renewals.yml, so the renewal calendar opens an issue 14 days before the Dependabot sweeper's token lapses.The token is the fine-grained PAT that ADR-0016 Decision 3 describes. The maintainer minted it and stored it in the main-only
dependabot-mergeenvironment at 2026-11-18T02:27Z, with a 366-day expiry: 2027-11-19. The entry follows the existingcredential-fleet-reports-patentry: its name, its category, the date, and a note on how to rotate it. It carries no value or account identifier, as the file's header requires.Checks
python3 ci/validate.pypasses, and the file parses as YAML with both credential entries present.🤖 Generated with Claude Code
https://claude.ai/code/session_01SjEL1LhqZs7gK6zG4STip2