Skip to content

build(deps): Bump actions/upload-artifact from 4 to 7 - #2

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

build(deps): Bump actions/upload-artifact from 4 to 7#2
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/upload-artifact-7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 15, 2026 •
edited
Loading

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 dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 15, 2026
spektre-labs pushed a commit that referenced this pull request Apr 17, 2026
@lauri-elias-rainio
feat(v102): first full σ-Eval-Harness run lands — BitNet numbers meas…
729f190 
…ured

Ran the v102 σ-Eval-Harness end-to-end on this host (Apple M3 / Metal /
bitnet.cpp i2_s) on 2026-04-17.  This is the first time the v29..v101
σ-stack has been driven against an external LLM eval suite on real
logits from real weights in this repo.  The scaffolding landed in the
previous commit; this commit adds two infrastructure pieces that were
needed to actually execute the run, and fills docs/v102/RESULTS.md with
the measured table.

Infrastructure:

  * benchmarks/v102/run_lm_eval.py — thin launcher that imports
    creation_os_backend before invoking lm_eval.cli_evaluate, so the
    `creation_os` model name is registered in lm_eval's registry at
    the moment argparse resolves `--model`.  Without this, setting
    PYTHONPATH is not enough (lm_eval does not import backends
    lazily from PYTHONPATH).

  * benchmarks/v102/_run_full.sh — reproducible driver for the
    full n=500 run across arc_easy, arc_challenge, truthfulqa_mc2;
    this is the command that `RESULTS.md` reproducibility stamp
    points at.

  * benchmarks/v102/run_eval.sh — now calls run_lm_eval.py instead
    of `python -m lm_eval` for the σ-gated path.

Results (see docs/v102/RESULTS.md for the full table + stderr):

  task             metric      σ-gated n=500   published (full)
  arc_easy         acc         0.762  ±0.019   0.708  (+5.4 pp, within 1σ)
  arc_challenge    acc_norm    0.488  ±0.022   0.498  (−1.0 pp, within 1σ)
  truthfulqa_mc2   acc         0.476  ±0.019   0.457  (+1.9 pp, within 1σ)

Total: 7 591 loglikelihood calls, ≈2 h 4 min wall, ≈1.0 ll_call/s
through the full stack (lm-eval → Python backend → --stdin RPC →
llama.cpp → σ-channels → JSON reply).

Interpretation (documented in RESULTS.md "Current outcome: #2"):

  σ-gated accuracy is statistically indistinguishable from Microsoft's
  published BitNet b1.58 2B-4T numbers on the three tasks measured.
  σ is a diagnostic channel; it does not (yet) translate into an
  accuracy lift, and no such claim is made anywhere in the repo.
  At τ = 0.0 (no abstain) this is the pre-registered "no regression"
  row — it had to match published BitNet numbers within stderr,
  otherwise the v101 bridge would be broken.  It does.

Tier updates:

  * docs/WHAT_IS_REAL.md — two pre-existing rows flip:
      "full ArcEasy / TruthfulQA-MC2 / GSM8K tables"  P → M
        (arc_easy / arc_challenge / truthfulqa_mc2 measured;
         MMLU / GSM8K remain P)
      "σ-gated acc strictly greater than baseline"    P → N
        (measured: σ is a neutral diagnostic at τ=0.0)
    and one new P row for the τ-sweep follow-up.

  * docs/ROADMAP_TO_AGI.md §5.0b — "End-to-end benchmark exposure of
    σ-stack" promoted to M; the priority-shortlist item #0 is struck
    through and replaced with the τ-sweep follow-up #0b.

What this commit does NOT claim:

  * No σ-gating accuracy lift (explicitly documented as neutral).
  * No coverage of MMLU / GSM8K / HellaSwag / Winogrande yet.
  * No improvement over any frontier model; the baseline is BitNet
    b1.58 2B-4T as published by Microsoft.

Reproducibility: bash benchmarks/v102/_run_full.sh on a host with the
GGUF checkpoint + .venv-bitnet + built creation_os_v101.  Raw lm-eval
outputs under benchmarks/v102/results/sigma_gated/qdpv68r5/ are
gitignored (large JSONL samples; the aggregated numbers and stamps in
RESULTS.md are the canonical record).

Made-with: Cursor
spektre-labs pushed a commit that referenced this pull request Apr 20, 2026
@lauri-elias-rainio
feat(sigma-pipeline): σ-photonic — optical rendering of the σ-gate (H2)
837708d 
σ-Photonic (H2) lifts the σ-gate onto an optical substrate.  The
formula is substrate-free: σ depends only on the ratio
I_max / Σ I_k, which is meaningful whether the channels are
transistor activations, spiking populations, or photodetector
taps on a Mach-Zehnder mesh.

Intensity σ:
  σ_photo = 1 − I_max / Σ I_k
  σ ≈ 0  ⇔ one channel dominates     (ACCEPT)
  σ ≈ 1  ⇔ intensity spread over N   (ABSTAIN)

Mach-Zehnder simulator:
  I_k = I_in · (1 + V cos Δφ_k) / 2
  V   visibility ∈ [0, 1]     (fringe contrast)
  Δφ  per-arm phase (radians)

Constructive arm (Δφ=0, V=1) collapses intensity onto that arm
→ σ = 0.  Destructive (Δφ=π, V=1) yields zero intensity on the
arm but the aggregate output becomes uniform → σ → 1 − 1/N.

Canonical demo (4 channels):
  dominant       — channel #2 holds 0.90/1.00 → σ = 0.10
  uniform        — four equal channels         → σ = 0.75
  mach_zehnder   — one Δφ=0 arm, three Δφ=π   → σ = 0.00 (V=1)

Files:
  src/sigma/pipeline/photonic.h       — API:
                                         sigma_from_intensities,
                                         mach_zehnder_sigma,
                                         cos_photon_channel_t.
  src/sigma/pipeline/photonic.c       — guards (NaN / negative /
                                         n ≤ 0 / V > 1), dominant /
                                         uniform / all-zero / MZI
                                         self-test cases, phase
                                         sweep σ = 0.5 check.
  src/sigma/pipeline/photonic_main.c  — JSON demo emitting all
                                         three scenarios.
  benchmarks/sigma_pipeline/check_sigma_photonic.sh
                                      — pins σ = 0.10 / 0.75 / 0.00
                                         plus argmax and intensities.

Note on scope: this is the σ-layer that consumes photonic
intensities (measured or simulated) — it is not an FDTD solver.
The H5 paper will cite the closed-form equivalence between the
digital and photonic gate outputs as the substrate-agnostic
guarantee.

Wired into the pipeline:
  Makefile         — creation_os_sigma_photonic +
                     check-sigma-photonic under
                     check-sigma-pipeline.
  .gitignore       — ignores the new binary.

Green against: check-sigma-photonic.
Next: H3 σ-substrate (vtable unifying digital / bitnet / spike /
photonic backends behind one σ-gate).

Made-with: Cursor
@dependabot dependabot Bot changed the title Bump actions/upload-artifact from 4 to 7 build(deps): Bump actions/upload-artifact from 4 to 7 Apr 20, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/upload-artifact-7 branch from 21e50fe to e726275 Compare April 20, 2026 21:03
@dependabot dependabot Bot changed the title build(deps): Bump actions/upload-artifact from 4 to 7 chore(deps): Bump actions/upload-artifact from 4 to 7 Apr 26, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/upload-artifact-7 branch from e726275 to 04a42dd Compare April 26, 2026 04:32
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/upload-artifact-7 branch from 04a42dd to d0680cd Compare May 3, 2026 09:55
@dependabot dependabot Bot changed the title chore(deps): Bump actions/upload-artifact from 4 to 7 build(deps): Bump actions/upload-artifact from 4 to 7 May 7, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/upload-artifact-7 branch 2 times, most recently from 230dfa3 to 42ed3eb Compare May 8, 2026 09:30
@dependabot
build(deps): Bump actions/upload-artifact from 4 to 7
e464be0 
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
dependabot Bot force-pushed the dependabot/github_actions/actions/upload-artifact-7 branch from 42ed3eb to e464be0 Compare May 8, 2026 12:35
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