Repository navigation
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: BabelQueue/babelqueue-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.19.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: BabelQueue/babelqueue-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.20.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 22 files changed
- 1 contributor
Commits on Oct 12, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 3a25b96 - Browse repository at this point
Copy the full SHA 3a25b96View commit details -
Configuration menu - View commit details
-
Copy full SHA for 96f377d - Browse repository at this point
Copy the full SHA 96f377dView commit details
Commits on Oct 17, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 72f5489 - Browse repository at this point
Copy the full SHA 72f5489View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a7d05e - Browse repository at this point
Copy the full SHA 0a7d05eView commit details -
Configuration menu - View commit details
-
Copy full SHA for b49b9df - Browse repository at this point
Copy the full SHA b49b9dfView commit details -
Add producer meta API, reject forbidden keys on encode, fold urn alia…
…s into job (1.20.0) EnvelopeCodec.make gains a keyword-only meta parameter; a collision with a core or forbidden meta key raises EnvelopeKeyError. encode now raises on forbidden keys and a top-level urn instead of dropping them. decode folds urn into job (blank ASCII job falls back to urn; job wins over urn with a warning). The conformance runner implements the 1.4.0 fields plus extension_write and encode_reject, with a runner self-test.
Configuration menu - View commit details
-
Copy full SHA for 558953a - Browse repository at this point
Copy the full SHA 558953aView commit details -
Decode raw bodies before re-encoding them in the runtime release, SQS…
… and Pulsar paths encode now rejects forbidden keys and a top-level urn, so paths that parsed a raw body and re-encoded it would raise on legacy bodies. Decode first (drops and warns, folds urn into job, keeps unknown keys). Adds regression tests for the runtime, SQS, Pulsar, Kafka and Azure Service Bus paths.
Configuration menu - View commit details
-
Copy full SHA for 40bfc10 - Browse repository at this point
Copy the full SHA 40bfc10View commit details -
Fix review round 1: mypy narrowing, urn-bearing RELEASE bodies, strin…
…g-only urn() - make(): build the meta block as Dict[str, Any] so mypy passes without ignores - raw RELEASE re-publish now normalises any body carrying a urn alias - urn()/accepts() require a string job; falsy non-string job counts as blank for the urn fold - CHANGELOG entries moved under [Unreleased]; has_forbidden_keys docstring notes urn exclusion
Configuration menu - View commit details
-
Copy full SHA for d2e1be7 - Browse repository at this point
Copy the full SHA d2e1be7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6299c42 - Browse repository at this point
Copy the full SHA 6299c42View commit details -
Configuration menu - View commit details
-
Copy full SHA for 87bde33 - Browse repository at this point
Copy the full SHA 87bde33View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2c31ac4 - Browse repository at this point
Copy the full SHA 2c31ac4View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.19.0...v1.20.0