Skip to content

Advance RFC #0830 "Evolving Ember's Major Version Process" to Stage Recommended #2212

Advance RFC #0830 "Evolving Ember's Major Version Process" to Stage Recommended

Advance RFC #0830 "Evolving Ember's Major Version Process" to Stage Recommended #2212

Triggered via pull request May 5, 2026 18:09
@ef4ef4
ready_for_review #1058
advance-rfc-0830
Status Success
Total duration 11s
Artifacts

newly-added-rfcs.yml

on: pull_request
Does PR add RFCs?
7s
Does PR add RFCs?
Stage must be 'Exploring' (via label) for new RFC before merging
0s
Stage must be 'Exploring' (via label) for new RFC before merging
RFC must be in only one stage before merging (labels)
0s
RFC must be in only one stage before merging (labels)
Only one RFC can be added in a PR
0s
Only one RFC can be added in a PR
Frontmatter stage must be 'accepted' before merging
0s
Frontmatter stage must be 'accepted' before merging
Filename matches RFC number
0s
Filename matches RFC number
Verify Accepted PR URL is correct
0s
Verify Accepted PR URL is correct
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Does PR add RFCs?
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, tj-actions/changed-files@v39. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/