Skip to content

ci: bump actions/upload-artifact from 4 to 7 - #9

Open
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/github_actions/actions/upload-artifact-7
Open

ci: bump actions/upload-artifact from 4 to 7#9
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/github_actions/actions/upload-artifact-7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 2, 2026

Copy link
Copy Markdown

Bumps actions/upload-artifact from 4 to 7.

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

... (truncated)

Commits
  • 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
  • 634250c Include changes in typespec/ts-http-runtime 0.3.5
  • e454baa Readme: bump all the example versions to v7 (#796)
  • 74fad66 Update the readme with direct upload details (#795)
  • bbbca2d Support direct file uploads (#764)
  • 589182c Upgrade the module to ESM and bump dependencies (#762)
  • 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
  • 02a8460 Add proxy integration test
  • b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
  • e516bc8 docs: correct description of Node.js 24 support in README
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Ibrar Ahmed and others added 4 commits September 2, 2026 23:37
The prefix was doing the schema's job. pgraft_get_cluster_status() said
pgraft twice and still left the whole extension sitting in public, next to
everything else in the database. So the prefix goes and the schema takes
over: 34 functions, 19 views and 3 tables, none of them in public any
more.

    pgraft.get_cluster_status()   pgraft.get_nodes()
    pgraft.add_node()             pgraft.member_list

Signatures and result columns are untouched, so a caller only has to
rewrite the name. One view had to be renamed outright: pgraft_kv_status
would have landed on pgraft.kv_status, which the etcd-style summary view
already occupies, so the key/value store's own health view is now
pgraft.kv_store_status.

The upgrade script has to clear out what 1.0 created, and the order
matters: views come down in reverse creation order so each one goes
before the view it selects from, then the functions. No CASCADE anywhere
-- if an object of yours depends on a pgraft function, the upgrade should
stop and tell you, not drop your object on the way past.

The apply path executes SQL of its own, so pgraft_json.c had to move with
it, or replicated writes would have started failing the moment the
extension was upgraded.
The SQL reference had drifted. set_debug, log_append, kv_list_keys,
kv_put_local and kv_delete_local were all documented returning something
they do not return, and four of the table-returning functions listed
columns that no longer exist anywhere -- get_queue_status was documented
as pending_msgs/processed_msgs/queue_full, which is not close to what it
actually gives you. Every signature on that page now matches the SQL, and
the 19 views, none of which were documented at all, are on it too.

The version requirements disagreed with themselves and with the build.
go.mod has needed Go 1.23 since the etcd/raft v3.6 bump, while the badge
said 1.21 and one page still said 1.15. The README claimed PostgreSQL 14
through 18 while four pages under docs/ demanded 17 or 18. The code has
carried a pre-15 path all along, so 14 is right and CI now proves it.
Nothing built or tested pgraft on a push. The workflows that existed
package releases and publish docs, both on workflow_dispatch, so a broken
SQL script or a compile error could sit on main indefinitely. CI now
builds against PostgreSQL 14 through 18 on every push and then does what
a compile cannot: creates the extension, checks that no object escaped
the pgraft schema, and selects from every view. That last check is what
would have caught the drop-order bug in the upgrade script.

The rest is scaffolding that was missing. CODE_OF_CONDUCT.md and
SUPPORT.md say how to behave here and where to take a question; the issue
and pull-request templates ask for the cluster state that makes a report
actionable; CODEOWNERS routes review; dependabot watches both the pinned
actions and the Go module; .editorconfig and .gitattributes keep
whitespace and line endings from drifting between contributors.
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 @github

dependabot Bot commented on behalf of github Sep 2, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: ci, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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.

0 participants