chore(deps): update workflows #36

renovate · 2024-03-07T02:30:22Z

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-artifact	action	minor	`v3.1.3` -> `v3.2.1`
gaurav-nelson/github-action-markdown-link-check	action	digest	`0f074c8` -> `1b916f2`
github/codeql-action	action	minor	`v2.24.7` -> `v2.28.1`
ossf/scorecard-action	action	minor	`v2.3.1` -> `v2.4.0`
pypa/gh-action-pypi-publish	action	minor	`v1.8.14` -> `v1.12.4`

Release Notes

actions/upload-artifact (actions/upload-artifact)

Notice: Breaking Changes ⚠️

We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.

See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.

What's Changed

V3 backport: Exclude hidden files by default by @SrRyan in https://github.com/actions/upload-artifact/pull/604

Full Changelog: actions/upload-artifact@v3.1.3...v3.2.0

github/codeql-action (github/codeql-action)

`v2.28.1`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

This is the last planned release of the v2. To continue getting updates for the CodeQL Action, please switch to v3.

2.28.1 - 10 Jan 2025

CodeQL Action v2 is now deprecated, and is no longer updated or supported. For better performance, improved security, and new features, upgrade to v3. For more information, see this changelog post. #2677
Update default CodeQL bundle version to 2.20.1. #2678

See the full CHANGELOG.md for more information.

`v2.28.0`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

This is the last planned release of the v2. To continue getting updates for the CodeQL Action, please switch to v3.

2.28.0 - 20 Dec 2024

Bump the minimum CodeQL bundle version to 2.15.5. #2655
Don't fail in the unusual case that a file is on the search path. #2660.

See the full CHANGELOG.md for more information.

`v2.27.9`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.9 - 12 Dec 2024

No user facing changes.

See the full CHANGELOG.md for more information.

`v2.27.8`

Compare Source

`v2.27.7`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.7 - 10 Dec 2024

We are rolling out a change in December 2024 that will extract the CodeQL bundle directly to the toolcache to improve performance. #2631
Update default CodeQL bundle version to 2.20.0. #2636

See the full CHANGELOG.md for more information.

`v2.27.6`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.6 - 03 Dec 2024

Update default CodeQL bundle version to 2.19.4. #2626

See the full CHANGELOG.md for more information.

`v2.27.5`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.5 - 19 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

`v2.27.4`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.4 - 14 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

`v2.27.3`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.3 - 12 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

`v2.27.2`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.2 - 12 Nov 2024

Fixed an issue where setting up the CodeQL tools would sometimes fail with the message "Invalid value 'undefined' for header 'authorization'". #2590

See the full CHANGELOG.md for more information.

`v2.27.1`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.1 - 08 Nov 2024

The CodeQL Action now downloads bundles compressed using Zstandard on GitHub Enterprise Server when using Linux or macOS runners. This speeds up the installation of the CodeQL tools. This feature is already available to GitHub.com users. #2573
Update default CodeQL bundle version to 2.19.3. #2576

See the full CHANGELOG.md for more information.

`v2.27.0`

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

2.27.0 - 22 Oct 2024

Bump the minimum CodeQL bundle version to 2.14.6. #2549
Fix an issue where the upload-sarif Action would fail with "upload-sarif post-action step failed: Input required and not supplied: token" when called in a composite Action that had a different set of inputs to the ones expected by the upload-sarif Action. #2557
Update default CodeQL bundle version to 2.19.2. #2552

See the full CHANGELOG.md for more information.

`v2.26.13`

Compare Source

`v2.26.12`

Compare Source

`v2.26.11`

Compare Source

`v2.26.10`

Compare Source

`v2.26.9`

Compare Source

`v2.26.8`

Compare Source

`v2.26.7`

Compare Source

`v2.26.6`

Compare Source

`v2.26.5`

Compare Source

`v2.26.4`

Compare Source

`v2.26.3`

Compare Source

`v2.26.2`

Compare Source

`v2.26.1`

Compare Source

`v2.26.0`

Compare Source

`v2.25.15`

Compare Source

`v2.25.14`

Compare Source

`v2.25.13`

Compare Source

`v2.25.12`

Compare Source

`v2.25.11`

Compare Source

`v2.25.10`

Compare Source

`v2.25.9`

Compare Source

`v2.25.8`

Compare Source

`v2.25.7`

Compare Source

`v2.25.6`

Compare Source

`v2.25.5`

Compare Source

`v2.25.4`

Compare Source

`v2.25.3`

Compare Source

`v2.25.2`

Compare Source

`v2.25.1`

Compare Source

`v2.25.0`

Compare Source

`v2.24.11`

Compare Source

`v2.24.10`

Compare Source

`v2.24.9`

Compare Source

`v2.24.8`

Compare Source

ossf/scorecard-action (ossf/scorecard-action)

`v2.4.0`

Compare Source

What's Changed

This update bumps the Scorecard version to the v5 release. For a complete list of changes, please refer to the v5.0.0 release notes. Of special note to Scorecard Action is the Maintainer Annotation feature, which can be used to suppress some Code Scanning false positives. Alerts will not be generated for any Scorecard Check with an annotation.

🌱 Bump github.com/ossf/scorecard/v5 from v5.0.0-rc2 to v5.0.0 by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1410
🐛 lower license sarif alert threshold to 9 by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1411

Documentation

docs: dogfooding badge by @jkowalleck in https://github.com/ossf/scorecard-action/pull/1399

New Contributors

@jkowalleck made their first contribution in https://github.com/ossf/scorecard-action/pull/1399

Full Changelog: ossf/scorecard-action@v2.3.3...v2.4.0

`v2.3.3`

Compare Source

[!NOTE]
There is no v2.3.2 release as a step was skipped in the release process. This was fixed and re-released under the v2.3.3 tag

What's Changed

🌱 Bump github.com/ossf/scorecard/v4 (v4.13.1) to github.com/ossf/scorecard/v5 (v5.0.0-rc1) by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1366
🌱 Bump github.com/ossf/scorecard/v5 from v5.0.0-rc1 to v5.0.0-rc2 by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1374
🌱 Bump github.com/ossf/scorecard/v5 from v5.0.0-rc2 to v5.0.0-rc2.0.20240509182734-7ce860946928 by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1377

For a full changelist of what these include, see the v5.0.0-rc1 and v5.0.0-rc2 release notes.

Documentation

📖 Move token discussion out of main README. by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1279
📖 link to ossf/scorecard workflow instead of maintaining an example by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1352
📖 update api links to new scorecard.dev site by @spencerschrock in https://github.com/ossf/scorecard-action/pull/1376

Full Changelog: ossf/scorecard-action@v2.3.1...v2.3.3

`v2.3.2`

Compare Source

pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)

`v1.12.4`

Compare Source

Be nice to FOSS maintainers.

✨ What's Changed

The main theme of this patch release that the support for uploading PEP 639 licensing metadata to PyPI has been fixed in #327.

🛠️ Internal Updates

A few smaller updates include the attestation existence being checked earlier in the process now, listing all the violating files together, not just one (PR #315).
And the lock file with the software available in runtime has been re-pinned in #329.
Additionally, the CI now runs the smoke-tests against both Ubuntu 22.04 and 24.04 explicitly via da900af.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.3...v1.12.4

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @woodruffw 💰 for releasing the license metadata support fix in Twine!

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

`v1.12.3`

Compare Source

✨ What's Improved

With the updates by @woodruffw 💰 and @webknjaz 💰 via #309 and #313, it is now possible to publish distribution packages that include core metadata v2.4, like those built using maturin. This is done by bumping Twine to v6.0.1 and pkginfo to v1.12.0.

📝 Docs

We've made an attempt to clarify the runtime and workflow shape that are expected to be supported for calling this action in: https://github.com/marketplace/actions/pypi-publish#Non-goals.

[!TIP]
Please, let us know in the release discussion if anything still remains unclear.
TL;DR always call [pypi-publish][pypi-publish] once per job; don't invoke it in reusable workflows; physically move building the dists into separate jobs having restricted permissions and storing the dists as GitHub Actions artifacts; when using self-hosted runners, make sure to still use [pypi-publish][pypi-publish] on a GitHub-provided infra with runs-on: ubuntu-latest, while building and testing may remain self-hosted; don't perform any other actions in the publishing job; don't call [pypi-publish][pypi-publish] from composite actions.

🛠️ Internal Updates

@br3ndonland 💰 improved the container image generation automation to include Git SHA in #301. And @woodruffw 💰 added the workflow_ref context to Trusted Publishing debug logging in #305, helping us diagnose misconfigurations faster. #313 also extends the smoke test in the CI to check against the maturin-made dists. Additionally, jeepney and secretstorage transitive deps have been added to the pip constraint-based lock file, as Dependabot seems to have missed those earlier.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.2...v1.12.3

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @samuelcolvin 💰 for nudging me to cut this release sooner and for sponsoring me via @pydantic 💰!

🔌 Shameless Plug: The other day I've made this 🦋 Bluesky 🇺🇦 FOSS Maintainers Starter Pack subscribe to read news from people like me :)

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

`v1.12.2`

Compare Source

🐛 What's Fixed

The fix for signing legacy zip sdists turned out to be incomplete, so @woodruffw 💰 promptly produced another follow-up that updated pypi-attestations from v0.0.13 to v0.0.15 in #297. This is the only change since the previous release.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.1...v1.12.2

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

`v1.12.1`

Compare Source

🐛 What's Fixed

Version v1.12.0 hit several rare corner cases we never considered fully supported, and this release fixes a few of those.
In #294, @webknjaz 💰 improved the self-hosted runner experience by pre-installing Python if it's not there, and with #293 the ability to use the action on GitHub Enterprise instances has been restored. The latter should've also fixed the ability to invoke [pypi-publish][pypi-publish] from nested in-repo composite actions — another exotic use-case that was never tested in our CI.
@woodruffw 💰 also managed to squeeze in a last-minute fix for detecting legacy .zip sdists while producing attestations via #295.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.0...v1.12.1

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Huge Thanks to all the bug reporters for posting the logs, helping inspect the problems and verify the regression fixes!

`v1.12.0`

Compare Source

⚡️ Why Should You Update?

This is a minor version bump, but it does not add any new user-facing interfaces. Still, I felt like it should not be a patch-release: this update brings significant changes to the action invocation and internal release process.

Previously, each invocation of [pypi-publish][pypi-publish] required building a container image in the invoking CI job. This was inefficient and added about 30 seconds to the publishing jobs at their startup just to build the container.

I wanted to improve this for over three years (#58) and a little over half a year ago @br3ndonland 💰 stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: #230.

Going forward, I'm going to pre-build per-version containers prior to cutting each release. And the action invocations will just pull the image from GitHub Container registry.

[!CAUTION]
Known quirks:

This seems to not work on self-hosted runners without a python executable: #289. The workaround could be installing it prior to running the action.

~Pinning to commit hashes does not work: #290. Workaround: postpone updating until it's fixed or switch to Git tags for now. Subscribe to that issue to follow the progress.~ UPD: This was an issue during the first 12 hours post release and it has been addressed upstream by publishing a commit SHA-tagged image for the release on Nov 12, 2024 at 10:27 UTC+1.

Calling pypi-publish from another nested repo-local composite action might be breaking file paths: #291. Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress.

Running within GitHub Enterprise fails on the action repo clone: #292. Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.11.0...v1.12.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

`v1.11.0`

Compare Source

🔏 Helping you become a trusted supply chain link 🔗

Two months ago, in v1.10.0, @woodruffw 💰 integrated support for generating and uploading PEP 740 digital attestations that can be used as provenance objects when analyzing dependency chains for the integrity.

To make sure it works well, it was implemented as an opt-in, so a relatively small subset of projects was able to try it out, and a few issues have been determined and fixed during this time.

That changes today! This version changes the feature toggle to “on by default”. This means that from now on, every project making use of Trusted Publishing will start producing and publishing digital attestations without having to do any modifications to how they use this action.

@woodruffw 💰 flipped the respective toggle in #277 with the possibility to opt-out.

🛠️ Internal Dependencies

@woodruffw 💰 bumped sigstore to v3.5.1 and pypi-attestations to v0.0.13 in lock files via #276.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.3...v1.11.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to William for working on improving the supply chain provenance in the ecosystem! The overall effort is tracked @&#https://github.com/pypi/warehouse/issues/15871/15871.

`v1.10.3`

Compare Source

💅 Cosmetic Output Improvements

In #270, @facutuesca 💰 made a follow-up to their previous PR #250, making the hints show up more granularly. This effectively makes sure that the suggestion to enable Trusted Publishing does not get displayed when it's already in use. It also makes the message nicer in a few places on the UI.

🛠️ Internal Dependencies

@mosfet80 💰 updated a few internal linter versions in #266, #267, and #271, no user impact. This is usually automated otherwise.

💪 New Contributors

@mosfet80 made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/266

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.2...v1.10.3

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

`v1.10.2`

Compare Source

💅 Cosmetic Output Improvements

In #250 and #258, @facutuesca 💰 added a nudge message with a magic link to pre-fill the creation of new Trusted Publishers configurations on PyPI. The users are now suggested to configure tokenless publishing by clicking a link printed in the job summary when it's detected that they publish to PyPI or TestPyPI. Just like magic! 🦄

🛠️ Internal Dependencies

@woodruffw 💰 bumped pypi-attestations to v0.0.12 in #262, fixing #263.

[!TIP]
Please keep in mind that reusable workflows are not yet supported, even though they sometimes work, mostly by accident.

💪 New Contributors

@facutuesca made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/258

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.1...v1.10.2

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @henryiii 💰 for promptly pointing up possible fixes for #263.

`v1.10.1`

Compare Source

🚑🔏 Oopsie... We missed a tiny bug in the attestations feature the other day

The problem was that the distribution file validity check was failing on any valid distribution being present and ready to be signed. What a silly mistake! It's now been fixed via pypa/gh-action-pypi-publish@0ab0b79, though. So everything's good!

-- @webknjaz 💰

[!IMPORTANT]
✨ Despite this minor hiccup, we invite you to still opt into trying this feature out early. It can be enabled like this:
  with:
    attestations: true
Leave feedback in the v1.10.0 release discussion or the PR.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.0...v1.10.1

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @hugovk 💰 for promptly validating the bug fix, mere minutes after I pushed it — I even haven't finished writing this text by then!

`v1.10.0`

Compare Source

🔏 Anything fancy, eh?

This time, @woodruffw 💰 implemented support for PEP 740 attestations functionality in #236 and #245. This is a big deal, as it is a huge step forward to replacing what the deprecated GPG signatures used to provide in a more meaningful way.

[!IMPORTANT]
✨ Please, do opt into trying this feature out early. It can be enabled as follows:
  with:
    attestations: true
Leave any feedback on this in this release discussion or the PR.

🙏 And please, thank William for working on this amazing improvement for the ecosystem! The overall effort is tracked @&#https://github.com/pypi/warehouse/issues/15871/15871, by the way.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.9.0...v1.10.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

`v1.9.0`

Compare Source

💅 Cosmetic Output Improvements

@woodruffw 💰 updated the tense on password nudge in #234
@shenxianpeng 💰 helped us disable the progress bar that was being produced by the twine upload command via #231
@woodruffw 💰 also linked the PyPI status dashboard in the trusted publishing error message via https://github.com/pypa/gh-action-pypi-publish/pull/243

🛠️ Internal Dependencies

pre-commit linters got auto-updated @ #225
some notable dependency bumps include
- cryptography == 42.0.7
- id == 1.4.0
- idna == 3.7 via #228
- requests == 2.32.0 via #240
- Twine == 5.1.0

⚙️ Secret Stuff

In #241, @br3ndonland 💰 added a Docker label linking the container image to this repository for GHCR to display it nicely. This is preparatory work for a big performance-focused refactoring he's working on in #230.

💪 New Contributors

@shenxianpeng made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/231
@br3ndonland made their first contribution in https://github.com/pypa/gh-action-pypi-publish/pull/241

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.8.14...v1.9.0

🧔‍♂️ Release Manager: @webknjaz 🇺🇦

🙏 Special Thanks to @pradyunsg 💰 for promptly unblocking this release to Marketplace as GitHub started asking for yet another developer agreement signature from the organization admins.

Configuration

📅 Schedule: Branch creation - "before 4pm on thursday" in timezone Australia/Sydney, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot added the dependencies label Mar 7, 2024

renovate bot changed the title ~~chore(deps): update github/codeql-action action to v2.24.6~~ chore(deps): update workflows Mar 8, 2024

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 8d207e2 to e64cbe4 Compare March 13, 2024 01:50

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from bf00d7f to e5089ae Compare March 17, 2024 23:40

renovate bot changed the title ~~chore(deps): update workflows~~ chore(deps): update gaurav-nelson/github-action-markdown-link-check digest to 25b2c43 Mar 17, 2024

renovate bot force-pushed the renovate/workflows branch 3 times, most recently from 5a08f6e to d6251b2 Compare March 18, 2024 00:53

renovate bot changed the title ~~chore(deps): update gaurav-nelson/github-action-markdown-link-check digest to 25b2c43~~ chore(deps): update workflows Mar 18, 2024

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 19049f1 to bdbdb0a Compare March 23, 2024 17:48

renovate bot force-pushed the renovate/workflows branch from bdbdb0a to a7348cc Compare April 7, 2024 02:43

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 68dcd83 to 7f259f5 Compare April 19, 2024 05:58

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from fa0feaf to c0fe8e8 Compare April 27, 2024 08:40

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from b76b705 to 9a4732c Compare May 13, 2024 17:54

renovate bot force-pushed the renovate/workflows branch from 9a4732c to 8e5f71a Compare May 22, 2024 23:50

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 0b514c4 to 73fdfea Compare June 5, 2024 08:44

renovate bot force-pushed the renovate/workflows branch 3 times, most recently from ab84a74 to 59b292b Compare June 17, 2024 05:13

renovate bot force-pushed the renovate/workflows branch from 59b292b to 2905925 Compare June 29, 2024 05:48

renovate bot force-pushed the renovate/workflows branch from 2905925 to ea80031 Compare July 12, 2024 17:28

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 2b10270 to 65c7be6 Compare July 26, 2024 03:01

renovate bot force-pushed the renovate/workflows branch 4 times, most recently from e448e4e to 2de266d Compare September 1, 2024 02:28

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from f1af59c to b3284f3 Compare September 4, 2024 17:37

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 097589a to 5df66e7 Compare September 20, 2024 14:59

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 4fbe8b2 to 8c9fdd4 Compare September 24, 2024 20:55

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 5165142 to 5fab41c Compare October 6, 2024 05:56

renovate bot force-pushed the renovate/workflows branch from 5fab41c to c1711ba Compare October 8, 2024 02:54

renovate bot force-pushed the renovate/workflows branch from c1711ba to 74e39a9 Compare October 15, 2024 23:59

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from ddda5ea to 1b1dec6 Compare October 30, 2024 05:48

renovate bot force-pushed the renovate/workflows branch 4 times, most recently from cb26af9 to f244b47 Compare November 13, 2024 14:45

renovate bot force-pushed the renovate/workflows branch from f244b47 to 30769d9 Compare November 14, 2024 17:45

renovate bot force-pushed the renovate/workflows branch from 30769d9 to e0588ff Compare November 22, 2024 02:41

renovate bot force-pushed the renovate/workflows branch 2 times, most recently from 24e008e to 7711b38 Compare December 11, 2024 02:42

renovate bot force-pushed the renovate/workflows branch from 7711b38 to 7461eb1 Compare December 14, 2024 04:29

renovate bot force-pushed the renovate/workflows branch from 7461eb1 to a3383ee Compare December 21, 2024 05:59

renovate bot force-pushed the renovate/workflows branch from a3383ee to 7009f13 Compare January 11, 2025 07:58

renovate bot force-pushed the renovate/workflows branch from 7009f13 to 59113c6 Compare January 20, 2025 12:03

chore(deps): update workflows

7b5dcde

renovate bot force-pushed the renovate/workflows branch from 59113c6 to 7b5dcde Compare January 24, 2025 03:47

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update workflows #36

chore(deps): update workflows #36

renovate bot commented Mar 7, 2024 •

edited

Loading

chore(deps): update workflows #36

Are you sure you want to change the base?

chore(deps): update workflows #36

Conversation

renovate bot commented Mar 7, 2024 • edited Loading

Release Notes

What's Changed

Notice: Breaking Changes ⚠️

What's Changed

CodeQL Action Changelog

2.28.1 - 10 Jan 2025

CodeQL Action Changelog

2.28.0 - 20 Dec 2024

CodeQL Action Changelog

2.27.9 - 12 Dec 2024

CodeQL Action Changelog

2.27.7 - 10 Dec 2024

CodeQL Action Changelog

2.27.6 - 03 Dec 2024

CodeQL Action Changelog

2.27.5 - 19 Nov 2024

CodeQL Action Changelog

2.27.4 - 14 Nov 2024

CodeQL Action Changelog

2.27.3 - 12 Nov 2024

CodeQL Action Changelog

2.27.2 - 12 Nov 2024

CodeQL Action Changelog

2.27.1 - 08 Nov 2024

CodeQL Action Changelog

2.27.0 - 22 Oct 2024

What's Changed

Documentation

New Contributors

What's Changed

Documentation

✨ What's Changed

🛠️ Internal Updates

✨ What's Improved

📝 Docs

🛠️ Internal Updates

🐛 What's Fixed

🐛 What's Fixed

⚡️ Why Should You Update?

🔏 Helping you become a trusted supply chain link 🔗

🛠️ Internal Dependencies

💅 Cosmetic Output Improvements

🛠️ Internal Dependencies

💪 New Contributors

💅 Cosmetic Output Improvements

🛠️ Internal Dependencies

💪 New Contributors

🚑🔏 Oopsie... We missed a tiny bug in the attestations feature the other day

🔏 Anything fancy, eh?

💅 Cosmetic Output Improvements

🛠️ Internal Dependencies

⚙️ Secret Stuff

💪 New Contributors

Configuration

renovate bot commented Mar 7, 2024 •

edited

Loading