[USERSNAP] I assume there is a valid reason that this proposal is marked as "expired" even though it is now 3/12 and the "expired" (expiration) date is 3/16. If there is a valid reason, then the phrasing seems to have a problem, as expired in the future... #885
bosko-madd-issue-to-project.yml
on: issues
Add issue to GovTool all project
3s
Add issue to governance tools community backlog project
5s
Annotations
2 errors and 2 warnings
|
|
|
Add issue to GovTool all project
Bad credentials - https://docs.github.com/rest
|
|
Add issue to governance tools community backlog project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/add-to-project@v1.0.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Add issue to GovTool all project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/add-to-project@v1.0.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|