build(deps): Bump actions/upload-artifact from 4 to 7#4
Merged
JohnMcLear merged 1 commit intoMay 5, 2026
Merged
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
2 times, most recently
from
29570eb to
2fedc1e
Compare
Member
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
2 times, most recently
from
17588df to
4999066
Compare
Member
|
@dependabot rebase |
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v4...v7) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
from
4999066 to
2540b3b
Compare
dependabot
Bot
deleted the
dependabot/github_actions/actions/upload-artifact-7
branch
JohnMcLear
added a commit
that referenced
this pull request
May 5, 2026
The first assertion in the test (rail icon visible after relaunch) used Playwright's default 15s expect timeout while the second assertion (tab restored) explicitly used 30s. On slow CI runners the cold restart routinely takes 8–12s before the rail finishes hydrating from getInitial, tipping the smaller budget over without any actual bug. Match the 30s used elsewhere. This has been the dominant CI flake across multiple PRs (#4, #10, #18, #20). Pinning a longer timeout doesn't mask a real bug — single- spec runs always pass in 3–4s; the flake is purely contention-driven. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
JohnMcLear
added a commit
that referenced
this pull request
May 5, 2026
* fix(snap): release to edge + stable in one upload publish-stable was failing v0.3.1 with: Status: error while processing - binary_sha3_384: Error checking upload uniqueness. …because both publish-edge and publish-stable uploaded the SAME artifact, and the Snap Store rejects byte-identical re-uploads. Collapse the two jobs into one \`publish\` job that uploads once and releases to both channels via snapcraft's comma-separated channel list (\`release: edge,stable\`). Drops the snap-store-stable environment dependency too, since user wants auto-publish without a manual gate; if a gate is wanted later, this can be re-introduced as either (a) re-split the jobs and use \`snapcraft release <revision> stable\` in the second to promote the existing edge revision, or (b) add \`environment: snap-store-stable\` back on this single job. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(test): bump restore-on-relaunch workspace-icon timeout to 30s The first assertion in the test (rail icon visible after relaunch) used Playwright's default 15s expect timeout while the second assertion (tab restored) explicitly used 30s. On slow CI runners the cold restart routinely takes 8–12s before the rail finishes hydrating from getInitial, tipping the smaller budget over without any actual bug. Match the 30s used elsewhere. This has been the dominant CI flake across multiple PRs (#4, #10, #18, #20). Pinning a longer timeout doesn't mask a real bug — single- spec runs always pass in 3–4s; the flake is purely contention-driven. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.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
1 participant
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 4 to 7.
Release notes
Sourced from actions/upload-artifact's releases.
... (truncated)
Commits
043fb46Merge pull request #797 from actions/yacaovsnc/update-dependency634250cInclude changes in typespec/ts-http-runtime 0.3.5e454baaReadme: bump all the example versions to v7 (#796)74fad66Update the readme with direct upload details (#795)bbbca2dSupport direct file uploads (#764)589182cUpgrade the module to ESM and bump dependencies (#762)47309c9Merge pull request #754 from actions/Link-/add-proxy-integration-tests02a8460Add proxy integration testb7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in README