Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge main into releases/v2 #1360

merged 22 commits into from Nov 14, 2022

Merge main into releases/v2 #1360

merged 22 commits into from Nov 14, 2022


Copy link

@github-actions github-actions bot commented Nov 14, 2022

Merging 33b10be into releases/v2

Conductor for this PR is @henrymercer.

Contains the following pull requests:

Please do the following:

  • Ensure the CHANGELOG displays the correct version and date.
  • Ensure the CHANGELOG includes all relevant, user-facing changes since the last release.
  • Check that there are not any unexpected commits being merged into the releases/v2 branch.
  • Ensure the docs team is aware of any documentation changes that need to be released.
  • Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.
  • Merge the mergeback PR that will automatically be created once this PR is merged.
  • Merge the v1 release PR that will automatically be created once this PR is merged.

henrymercer and others added 22 commits November 1, 2022 16:59
Mergeback v2.1.31 refs/heads/releases/v2 into main

Enable file baseline information behind a feature gate
Suppose a customer has a run where the init Action failed before saving
a config file.
When the customer opens their Actions logs, the UI currently focuses on
the post init step, since this is the last step that failed.
Demoting the error in the post init Action to a warning means that the
UI will instead focus on the `init` step, which is more useful for
debugging what went wrong.

Improve experience when init fails before generating a config file
use ATM pack v0.4.0 for CLI v2.11.3 and above
Force exit of process if a timeout has occurred
npm v9 is not compatible with Node 12, so we can't update to it yet.
@henrymercer henrymercer marked this pull request as ready for review November 14, 2022 12:05
@henrymercer henrymercer requested a review from a team as a code owner November 14, 2022 12:05
@henrymercer henrymercer merged commit 4238421 into releases/v2 Nov 14, 2022
335 checks passed
@henrymercer henrymercer deleted the update-v2.1.32-33b10be6 branch November 14, 2022 12:35
@github-actions github-actions bot mentioned this pull request Nov 14, 2022
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

4 participants