Repository navigation
Conversation
dependabot
Bot
added
dependencies
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v6...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/develop/actions/upload-artifact-7
branch
from
September 8, 2026 21:39
a3e3a6e to
91057e2
Compare
dependabot
Bot
deleted the
dependabot/github_actions/develop/actions/upload-artifact-7
branch
September 8, 2026 21:39
lorem-dev
added a commit
that referenced
this pull request
Sep 8, 2026
download-artifact v7 -> v8 and tauri-action v0.6.2 -> v1.0.0, landed in one commit because they only ever run together and each one's Dependabot pull request went stale the moment the other merged. upload-artifact v6 -> v7 went ahead of them in #54. Neither is exercised by any pull request: release.yml runs on a tag and nothing else. What follows is the compatibility review that stands in for a check, per change. download-artifact v8 has the one real breaking change of the three. A digest mismatch is now an error rather than a warning, and the action no longer unzips a download whose Content-Type says it is not a zip. Both exist to support v7's direct (unzipped) uploads; this pipeline uploads ordinary zipped artifacts and downloads them in the same run, so the second is inert and the first is a straight gain -- a corrupted transfer now fails the release instead of publishing a damaged asset. tauri-action v1.0.0 carries eight breaking changes and none of them reach this workflow: - The step passes `projectPath` and `args`, nothing else. The renamed inputs (assetNamePattern, includeUpdaterJson) and the removed ones (includeRelease, includeDebug, updaterJsonKeepUniversal, project auto-init) are all unused. - No `tagName`, so this is the build-only path and the new "update the name and body of an existing release" behaviour cannot fire. The publish job still owns the release and its CHANGES.md notes. - `.app.tar.gz` and its signature now carry the version. Nothing here reads them: "Stage release assets" collects an explicit extension allowlist (dmg, deb, rpm, AppImage, msi, exe, msix, and the two skillkeeper-cli archives), which never included the updater bundles. - Tauri v1 and unstable v2 support is dropped; this app is on 2.11.5. Two v1 changes do land on this layout, and the workflow already satisfies both. Runner detection now fails loudly when a lockfile is present but its package manager is not installed -- corepack and `pnpm install --frozen-lockfile` both run before this step. And lockfile detection now walks up the tree, so with `projectPath: apps/desktop` and the only pnpm-lock.yaml at the repository root, v1 finds a lockfile where v0.6.2 found none. The worst case there is a redundant install. The real check is a release candidate: RC tags are cut from develop, publish as a pre-release, and releases/latest/download never resolves to a pre-release, so one cannot reach install.sh users.
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 6 to 7.
Release notes
Sourced from actions/upload-artifact's releases.
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 test