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/v3 into releases/v2 #2036

Merged
merged 32 commits into from Dec 13, 2023
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 13, 2023

Merging b374143 into releases/v2.

Conductor for this PR is @nickfyson.

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.
  • 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.

nickfyson and others added 23 commits December 7, 2023 14:07
Mergeback v2.22.10 refs/heads/releases/v2 into main
* Bump the actions group with 2 updates

Bumps the actions group with 2 updates: [actions/setup-python](https://github.com/actions/setup-python) and [actions/setup-go](https://github.com/actions/setup-go).


Updates `actions/setup-python` from 4 to 5
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v4...v5)

Updates `actions/setup-go` from 4 to 5
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/setup-go
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>

* Rebuild

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Henry Mercer <henry.mercer@me.com>
Co-authored-by: Henry Mercer <henry.mercer@me.com>
change to node20 for all actions
@github-actions github-actions bot added the Update dependencies Trigger PR workflow to update dependencies label Dec 13, 2023
@nickfyson nickfyson marked this pull request as ready for review December 13, 2023 15:24
@nickfyson nickfyson requested a review from a team as a code owner December 13, 2023 15:24
@github-actions github-actions bot removed the Update dependencies Trigger PR workflow to update dependencies label Dec 13, 2023
Copy link
Contributor Author

Pushed a commit to update the checked-in dependencies. Please mark the PR as ready for review to trigger PR checks.

@github-actions github-actions bot marked this pull request as draft December 13, 2023 15:31
Copy link
Contributor Author

Pushed a commit to rebuild the Action. Please mark the PR as ready for review to trigger PR checks.

@github-actions github-actions bot marked this pull request as draft December 13, 2023 18:44
@nickfyson nickfyson marked this pull request as ready for review December 13, 2023 18:47
@nickfyson nickfyson added the Update dependencies Trigger PR workflow to update dependencies label Dec 13, 2023
@github-actions github-actions bot removed the Update dependencies Trigger PR workflow to update dependencies label Dec 13, 2023
Copy link
Contributor Author

Pushed a commit to update the checked-in dependencies. Please mark the PR as ready for review to trigger PR checks.

@github-actions github-actions bot marked this pull request as draft December 13, 2023 20:08
@nickfyson nickfyson added the Rebuild Re-transpile JS & re-generate workflows label Dec 13, 2023
@github-actions github-actions bot removed the Rebuild Re-transpile JS & re-generate workflows label Dec 13, 2023
Copy link
Contributor Author

Pushed a commit to rebuild the Action. Please mark the PR as ready for review to trigger PR checks.

@nickfyson nickfyson marked this pull request as ready for review December 13, 2023 20:11
@nickfyson nickfyson merged commit 03e7845 into releases/v2 Dec 13, 2023
357 checks passed
@nickfyson nickfyson deleted the backport-v2.22.11-b374143c1 branch December 13, 2023 20:40
@jsoref
Copy link
Contributor

jsoref commented Jan 25, 2024

@henrymercer could you please adjust the description?

It says:

But that was reverted.

@henrymercer
Copy link
Contributor

Good call, thanks.

@jsoref
Copy link
Contributor

jsoref commented Jan 25, 2024

Thanks. That's exactly what I and the person after me need in order to understand what's going on!

(Items in release notes or the top level readme would also help, but this is much better than nothing.)

@henrymercer
Copy link
Contributor

We've added a section to the top of the changelog, as well as a "[v3+ only] The CodeQL Action now runs on Node.js v20" changelog note for 3.22.11. We're also looking to see whether we can use GitHub Releases to better communicate the changenotes for each release, but we need to look at how this impacts the CodeQL Bundle which is also distributed via GitHub Releases.

@jsoref
Copy link
Contributor

jsoref commented Jan 25, 2024

At the expense of burning a commit on the default branch, I'd put a thing into https://github.com/github/codeql-action?tab=readme-ov-file#codeql-action

At least until you fix the releases tab. Making people search through all releases only to find nothing isn't great.

(I'm trying to release my own action and dealing w/ the fallout from the node v20 changes....)

@henrymercer
Copy link
Contributor

Thanks for the suggestion, I'm happy to err on the side of over-communicating :) See #2100

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.

None yet

4 participants