Repository navigation
Update Versions - #218
Open
github-actions[bot] wants to merge 2 commits into
Open
Update Versions#218github-actions[bot] wants to merge 2 commits into
github-actions[bot] wants to merge 2 commits into
Conversation
github-actions
Bot
force-pushed
the
changepacks/main
branch
6 times, most recently
from
November 13, 2026 17:12
4efbb15 to
c0a7a23
Compare
github-actions
Bot
force-pushed
the
changepacks/main
branch
from
November 13, 2026 17:30
175b196 to
5d7368f
Compare
This branch has not been deployed
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.
Changepacks
vespera@0.6.0 → 0.7.0 - crates/vespera/Cargo.toml
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera_core@0.6.0 → 0.7.0 - crates/vespera_core/Cargo.toml
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera_inprocess@0.6.0 → 0.7.0 - crates/vespera_inprocess/Cargo.toml
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera_jni@0.6.0 → 0.7.0 - crates/vespera_jni/Cargo.toml
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera_macro@0.6.0 → 0.7.0 - crates/vespera_macro/Cargo.toml
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera-bridge@0.6.0 → 0.7.0 - libs/vespera-bridge/build.gradle.kts
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.vespera-bridge-gradle-plugin@0.6.0 → 0.7.0 - libs/vespera-bridge-gradle-plugin/build.gradle.kts
Minor
vespera_dispatch_asyncnow honours the async in-flight cap (shared with JNIdispatchAsync, default 4096, over the cap → inline 503), and C hosts can set runtime, limit, deadline and async-cap knobs with the newvespera_configure_*functions (VESPERA_ERR_TOO_LATEonce fixed) instead of environment variables.vespera::cron::shutdown_and_waitcan no longer report idle while a cron run is starting: a tick that wakes up as shutdown begins now backs out instead of launching its job.#[vespera::cron]jobs declared insrc/lib.rs/src/main.rsor inside an inlinemodnow resolve to their real module path (previouslycrate::lib::jobfailed to compile and inline module segments were dropped), and a job declared aftervespera!in a file that already has registered jobs is no longer skipped.serialNumber(a reproducible UUID of name, version and commit), whichactions/attestrequires — the 0.6.0 release attested provenance but its SBOM attestations were rejected as "Unsupported SBOM format".scripts/sbom.shchecks the field on every PR. No API change.route(e.g. /users/{id}) instead of the raw requestpath, so secrets in path segments no longer reach logs.