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 releases/v2 into releases/v1 #1362

Merged
merged 28 commits into from
Nov 14, 2022
Merged

Conversation

github-actions[bot]
Copy link
Contributor

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

Merging 4238421 into releases/v1

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/v1 branch.
  • Ensure the docs team is aware of any documentation changes that need to be released.
  • Remove and re-add the "Update dependencies" label to the PR to trigger just this workflow.
  • Wait for the "Update dependencies" workflow to push a commit updating the dependencies.
  • Mark the PR as ready for review to trigger the full set of PR checks.
  • Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.

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

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.
…nit-fails

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.
@github-actions github-actions bot added the Update dependencies Trigger PR workflow to update dependencies label Nov 14, 2022
@henrymercer henrymercer removed the Update dependencies Trigger PR workflow to update dependencies label Nov 14, 2022
@henrymercer henrymercer added the Update dependencies Trigger PR workflow to update dependencies label Nov 14, 2022
@github-actions github-actions bot removed the Update dependencies Trigger PR workflow to update dependencies label Nov 14, 2022
@henrymercer henrymercer marked this pull request as ready for review November 14, 2022 12:58
@henrymercer henrymercer requested a review from a team as a code owner November 14, 2022 12:58
henrymercer
henrymercer previously approved these changes Nov 14, 2022
@henrymercer
Copy link
Contributor

The "Update dependencies" label triggered a workflow run using the version on releases/v1 that has not yet been patched to use npm v8 (that patch is included in this PR but is not yet on the branch). Therefore the "Update checked-in dependencies" commit that was pushed is wrong. I'll create one manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants