Skip to content

ci(deps): bump actions/upload-artifact from 5 to 7#2

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/actions/upload-artifact-7
Open

ci(deps): bump actions/upload-artifact from 5 to 7#2
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/actions/upload-artifact-7

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Apr 8, 2026

Bumps actions/upload-artifact from 5 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

Commits
  • 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
  • ddc45ed docs: update README to correct action name for Node.js 24 support
  • 615b319 chore: release v6.0.0 for Node.js 24 support
  • 017748b Merge pull request #744 from actions/fix-storage-blob
  • 38d4c79 chore: rebuild dist
  • 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)

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 5 to 7.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v5...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 dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 8, 2026
thatcooperguy added a commit that referenced this pull request Apr 8, 2026
Part 2 of the 0.7.0 production-safety push. Closes audit findings
#1, #2, #3, #5 from the bug hotspot audit — WebSocket endpoints
were missing the telemetry hooks their HTTP counterparts had, and
council synthesis was bypassing budget enforcement.

/v1/ws/query — observability hooks
-----------------------------------
Streaming queries now call engine.rate_manager.record_success /
record_failure and engine._log_query() the same way the HTTP path
does. Previously WebSocket queries were invisible to analytics,
the budget tracker, and the circuit breaker — a provider could
die mid-stream and the rate manager would never see the failure,
so the next query would hit the same dead provider.

Mid-stream disconnects now record a failure too (a client hanging
up mid-response is almost always caused by provider stall, not a
clean user exit, and we want the rate manager to see that signal).

/v1/ws/council — query logging
------------------------------
After council_complete, walks every member response + the synthesis
and calls engine._log_query() so WS councils show up in
/v1/analytics, /v1/budget/status, and conversation history. Before
this, running `nvh convene` via the webui left zero trace in any
dashboard — users genuinely thought their queries had vanished.

Council pre-synthesis budget check
----------------------------------
CouncilOrchestrator.run_council_streaming now takes an optional
`budget_check` coroutine. When members collectively blow through
the daily/monthly limit, synthesis is blocked before it fires
another LLM call, and the client receives an `error` event with
phase="synthesis_budget" so the UI can explain why the session
stopped. The API layer wires engine._check_budget into this hook
so the council orchestrator doesn't need to know about engine
internals.

Rate manager exception logging
------------------------------
Replaced 5 `except Exception: pass` blocks around rate_manager.
record_success / record_failure with `logger.debug(...)` so
telemetry failures are at least visible. The two remaining bare
excepts in council.py (_is_healthy fallback, agreement scorer
fallback) are intentional — both flagged as safe by the audit.

Test suite: 225 -> 226 passing (new version consistency test).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants