Repository navigation
Restore automated BSL change date updates - #4016
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
|
Subscribed to pull request
Generated by CodeMention Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4016 +/- ##
=======================================
Coverage 60.52% 60.52%
=======================================
Files 955 955
Lines 42081 42081
Branches 8835 8835
=======================================
Hits 25465 25465
Misses 16522 16522
Partials 94 94 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
⏩ The changelog entry check has been skipped since the "no changelog" label is present. |
Summary
expo/eas-buildLICENSE-BUSLinstead of the former repository's rootLICENSEmain, then every three monthsWhy
The EAS Build packages moved into this repository, but their scheduled BSL change-date automation was not moved with them. As a result,
LICENSE-BUSLstill has the last date written by the archived repository.After this workflow lands on
main, its path-based push trigger will advance the stale change date and future scheduled runs will keep it three years ahead.The workflow deliberately does not run on pull requests because it uses the write-capable
EXPO_BOT_PAT. Existing production evidence confirms that token can update the protected default branch:Release workflowrun 29394979387 successfully pushedmain -> mainon July 15, 2026 using the same repository secret.Validation
actionlint .github/workflows/license.ymlgit diff --check