Update GitHub Action to github-script@v8 #33634

pull MamunC0der wants to merge 1 commits into bitcoin:master from MamunC0der:patch-1 changing 1 files +1 −1
  1. MamunC0der commented at 6:40 PM on October 15, 2025: contributor

    Version v8 introduces performance improvements, enhanced JavaScript runtime support, and updated dependencies for greater security and reliability. Release notes: actions/github-script@v8: https://github.com/actions/github-script/releases/tag/v8

  2. Update action.yml 478047668e
  3. DrahtBot commented at 6:40 PM on October 15, 2025: contributor

    <!--e57a25ab6845829454e8d69fc972939a-->

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    <!--006a51241073e994b41acfe9ec718e94-->

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33634.

    <!--021abf342d371248e50ceaed478a90ca-->

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

    <!--5faf32d7da4f0f540f40219e4f7537a3-->

  4. fanquake commented at 10:30 AM on October 16, 2025: member
  5. willcl-ark commented at 10:44 AM on October 16, 2025: member

    Not sure there is any need to bump this myself. I think we should probably adopt a ~ policy to only bump when:

    • a version is nearing End of Life
    • we want a new feature from a new version
    • other unknown reason arises

    Its hard to say whether "randomly bumping to new versions" is more or less likely to cause issues than sticking around on older versions, and if we need to update eventually then perhaps the difference is exactly nothing. But I don't see a compelling reason to do this now.

  6. fanquake commented at 10:45 AM on October 16, 2025: member

    Closing for now.

  7. fanquake closed this on Oct 16, 2025

  8. maflcko commented at 11:48 AM on October 16, 2025: member

    policy

    I think the policy is "Ensure your workflows use the latest versions of actions that are running on Node 20. For more information, see Using Versions for Actions.". Source: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/#for-actions-users

    Something similar may happen with node-24. However, I am not familiar with GHA, JavaScript, or Node, or npm, so I can't evaluate if any of this applies here.


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me