chore(deps): bump actions/upload-artifact from 3.pre.node20 to 4.3.3#133
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
chore(deps): bump actions/upload-artifact from 3.pre.node20 to 4.3.3#133dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.pre.node20 to 4.3.3. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@97a0fba...6546280) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
jmeridth
added a commit
that referenced
this pull request
May 8, 2024
Closes #133, Closes #134, Closes #135, Close #137 To minimize the number of pull requests we get from dependabot, using groups will help with this. Still want major semver changes to be single PRs so that stand out and we pay particular attention to them. - [x] handle our multiple github action updates while in here. Signed-off-by: jmeridth <jmeridth@gmail.com>
5 tasks
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
zkoppert
added a commit
that referenced
this pull request
Feb 27, 2026
Replace plain requirements.txt with hash-pinned dependencies generated by pip-compile --generate-hashes, and add --require-hashes to the pip install command in the Dockerfile. This resolves code scanning alert #133 (pip install without hash verification) by ensuring all packages are verified against known hashes during installation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
zkoppert
added a commit
that referenced
this pull request
Feb 27, 2026
Add requirements-docker.txt with hash-pinned dependencies (generated via pip-compile --generate-hashes) and use --require-hashes in the Dockerfile pip install command. The original requirements.txt is kept for development/CI use, while requirements-docker.txt includes all transitive dependencies with SHA256 hashes for supply chain security. Resolves code scanning alert #133. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
zkoppert
added a commit
that referenced
this pull request
Feb 28, 2026
Expand requirements.txt to include all transitive dependencies (via pip-compile) and use --no-deps in the Dockerfile to prevent pip from fetching any packages not explicitly listed. This resolves code scanning alert #133 by ensuring only explicitly pinned packages are installed, mitigating supply chain risks from unexpected transitive dependency resolution. The fully-resolved requirements.txt remains dependabot-friendly since each pin can be updated independently. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
zkoppert
added a commit
that referenced
this pull request
Feb 28, 2026
Expand requirements.txt to include all transitive dependencies (via pip-compile) and use --no-deps in the Dockerfile to prevent pip from fetching any packages not explicitly listed. This resolves code scanning alert #133 by ensuring only explicitly pinned packages are installed, mitigating supply chain risks from unexpected transitive dependency resolution. The fully-resolved requirements.txt remains dependabot-friendly since each pin can be updated independently. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/upload-artifact from 3.pre.node20 to 4.3.3.
Release notes
Sourced from actions/upload-artifact's releases.
... (truncated)
Commits
6546280updating package versionc004fb4Merge branch 'main' into eggyhead/use-artifact-v2.1.690aba49updating toolkit artifact dependency to 2.1.6b06cde3Merge pull request #563 from actions/eggyhead/release-4.3.21746f4aRevert "updating to release 4.3.2"31685d0updating to release 4.3.218bf333Merge pull request #562 from actions/eggyhead/update-artifact-v215dac413bupdate package lock versionbb3b4a3updating package version3e3da83updating artifact and core dependenciesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)