Skip to content

chore(deps): bump softprops/action-gh-release from 1 to 3 - #3

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/softprops/action-gh-release-3
Open

chore(deps): bump softprops/action-gh-release from 1 to 3#3
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/softprops/action-gh-release-3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps softprops/action-gh-release from 1 to 3.

Release notes

Sourced from softprops/action-gh-release's releases.

v3.0.0

3.0.0 is a major release that moves the action runtime from Node 20 to Node 24. Use v3 on GitHub-hosted runners and self-hosted fleets that already support the Node 24 Actions runtime. If you still need the last Node 20-compatible line, stay on v2.6.2.

What's Changed

Other Changes 🔄

  • Move the action runtime and bundle target to Node 24
  • Update @types/node to the Node 24 line and allow future Dependabot updates
  • Keep the floating major tag on v3; v2 remains pinned to the latest 2.x release

v2.6.2

What's Changed

Other Changes 🔄

Full Changelog: softprops/action-gh-release@v2...v2.6.2

v2.6.1

2.6.1 is a patch release focused on restoring linked discussion thread creation when discussion_category_name is set. It fixes [#764](https://github.com/softprops/action-gh-release/issues/764), where the draft-first publish flow stopped carrying the discussion category through the final publish step.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

Bug fixes 🐛

v2.6.0

2.6.0 is a minor release centered on previous_tag support for generate_release_notes, which lets workflows pin GitHub's comparison base explicitly instead of relying on the default range. It also includes the recent concurrent asset upload recovery fix, a working_directory docs sync, a checked-bundle freshness guard for maintainers, and clearer immutable-prerelease guidance where GitHub platform behavior imposes constraints on how prerelease asset uploads can be published.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

... (truncated)

Changelog

Sourced from softprops/action-gh-release's changelog.

0.1.13

  • fix issue with multiple runs concatenating release bodies #145

0.1.12

  • fix bug leading to empty strings substituted for inputs users don't provide breaking api calls #144
Commits
  • b430933 release: cut v3.0.0 for Node 24 upgrade (#670)
  • c2e35e0 chore(deps): bump the npm group across 1 directory with 7 updates (#783)
  • 3bb1273 release 2.6.2
  • c34030f chore: bump node to 24.14.1
  • 8975bd0 chore(deps): bump vite from 8.0.0 to 8.0.5 (#781)
  • f71937f chore(deps): bump brace-expansion from 5.0.4 to 5.0.5 (#777)
  • 3f0d239 chore(deps): bump picomatch from 4.0.3 to 4.0.4 (#775)
  • 153bb8e release 2.6.1
  • 569deb8 fix: preserve discussion category when publishing releases (#765)
  • 26e8ad2 release 2.6.0
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 2, 2026
@dependabot
chore(deps): bump softprops/action-gh-release from 1 to 3
95ae932 
Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 1 to 3.
- [Release notes](https://github.com/softprops/action-gh-release/releases)
- [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
- [Commits](softprops/action-gh-release@v1...v3)

---
updated-dependencies:
- dependency-name: softprops/action-gh-release
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/softprops/action-gh-release-3 branch from 6c91e23 to 95ae932 Compare May 2, 2026 21:44
mevBlaze added a commit that referenced this pull request Jul 1, 2026
@mevBlaze @claude
fix(oracle_health): canary uses oracle_query singleton path + top-3-a…
979e3fc 
…bove-R67 PASS criteria

_run_canary() previously created fresh TreeVectorService+TreeSearch and used
rerank=True — giving different results than the real oracle_query code path
(singleton, rerank=False). The lock appeared at rank #1 (reranker-boosted)
in the canary but rank #3 in real queries — a false-positive PASS signal.

Fix:
- Use get_search() singleton (same as handle_query / oracle_query)
- rerank=False, include_synthesis=True — exact handle_query signature
- Over-fetch top_k*5, post-filter channel:raw in Python — mirrors handle_query
- Handle _vectors=None gracefully (SKIP status instead of ERROR)

PASS criteria updated (rigid #1 was a brittle false-fail):
- Lock (OBS-axxis-20260430-1519) must be in TOP-3
- Lock must rank above R67 ruling (OBS-axxis-20260429-1324/1328)
Newer high-relevance Blaze decisions legitimately rank above the lock (same
×1.8 policy boost but higher recency/Hebbian) — they belong above it.

Canary verified live: rank #3 score 0.6644, R67 obs absent from top-10
(correctly demoted far below), PASS → oracle_health GREEN HEALTHY.

Score-drop investigation (0.9126 earlier this session → 0.6644 now):
NOT densification. NOT PageRank dilution (PageRank not in blend_scores).
Root cause: two new Blaze obs created TODAY (OBS-piper-20260630-006/008)
have recency≈1.0 (created hours ago) vs lock's recency≈0.0 (61 days,
lambda=0.01/hour → e^-14.6≈0) and Hebbian 160/70 vs lock's 12. These
raise max_rrf and max_heb normalization denominators, reducing the lock's
normalized blend score. Expected correct behavior — not a regression.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016jtEm8s9mxR2GmPScq13At
mevBlaze added a commit that referenced this pull request Jul 1, 2026
@mevBlaze @claude
fix(oracle_health): canary uses singleton + rerank=True (anti-rot Rul…
1d77694 
…e 9, user-facing path)

Previous fix used rerank=False (oracle_query agent path) — wrong for the canary.
Anti-rot Rule 9: user-facing /search defaults rerank=True. The canary tests whether
the brain correctly surfaces locked decisions to users — that's the user-facing path.

The original bug was fresh TreeVectorService instances (cold vector index, unstable
candidates) not the rerank=True choice. Fix keeps the singleton (warm, stable) and
restores rerank=True (TEI cross-encoder, port 4085).

Verified live: lock OBS-axxis-20260430-1519 at rank #1 score 1.7892, R67 ruling
OBS-axxis-20260429-1328 at #3 (below lock), OBS-axxis-20260429-1324 absent —
oracle_health GREEN HEALTHY.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016jtEm8s9mxR2GmPScq13At
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants