Skip to content

[pull] main from apache:main#172

Merged
pull[bot] merged 3 commits into
sudoevans:mainfrom
apache:main
May 12, 2026
Merged

[pull] main from apache:main#172
pull[bot] merged 3 commits into
sudoevans:mainfrom
apache:main

Conversation

@pull

@pull pull Bot commented May 12, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

* ci: gate merging on a single Release Validation summary job

Adds a "summary" job to release-validation.yml that depends on
check-paths, build-artifacts, and install-and-smoke and runs
with if: always(). It translates the upstream conclusions into
a single binary verdict — success/skipped → pass, failure or
cancelled → fail — so the required check has a stable name and
a definite state regardless of whether upstream jobs ran or
were path-filtered out.

In .asf.yaml the required contexts drop from two matrix-suffixed
names ("Release Validation / build-artifacts", "Release Validation
/ install-and-smoke (3.12)") to one: "Release Validation / summary".

Why this is needed:
- PRs that only touch docs/ or website/ trigger check-paths to
  set should_run=false, which skips the heavy jobs.
- GitHub treats SKIPPED jobs as non-passing for required-status-
  checks, so those PRs were stuck in BLOCKED state forever
  (see commit a655edf for the previous attempt that didn't
  work for this exact reason).
- The summary job sidesteps the SKIPPED ambiguity because it
  always runs and always produces a definite SUCCESS or FAILURE.

Real code PRs are unaffected: if any release-validation job
fails, the summary fails, and merging is blocked.

* style: run black on burr/core/graph.py

Drive-by fix — `f7a1750d` (rename shadowed `format` builtin)
left this file black-non-compliant for line-length=100. Caught
by pre-commit on this branch.
* website: add Downloads page per ASF release policy

Adds a /downloads route covering the 0.42.0-incubating and 0.41.0-incubating
releases with mirror-selection links for tarballs, direct HTTPS links for
signatures and checksums, GPG/SHA-512 verification instructions, and the
standard incubator disclaimer. Adds a "Download" entry to the navbar.

Addresses the IPMC vote feedback that burr.apache.org needs a public
download page per https://www.apache.org/legal/release-policy.html#publication.

The repo-root .gitignore has a `downloads/` rule (Python packaging), which
shadows the new Next.js app-router directory; a negation rule is added in
website/.gitignore to re-include it.

* website: restructure downloads page for end users

Lead with install + UI launch + quick links, then ASF source
releases, then verification. Apache compliance content is still
present but no longer the first thing a Python dev sees.

Also: flag 0.41.0 PyPI packaging issues with a note on its release
card, and render version headings as "X.Y.Z (incubating)" rather
than "X.Y.Z-incubating".
The PyPI package was renamed to apache-burr at the 0.41.0
release, but ~30 files in docs, examples, and a few error
messages still tell users to `pip install burr[...]`. That
doesn't work — PyPI's `burr` is a placeholder.

This is a pure mechanical sweep that only touches `pip install`
invocations. Module imports (`import burr`, `from burr...`),
the `burr` CLI command name, and file paths are untouched.
@pull pull Bot locked and limited conversation to collaborators May 12, 2026
@pull pull Bot added the ⤵️ pull label May 12, 2026
@pull pull Bot merged commit 83f2ea8 into sudoevans:main May 12, 2026
21 of 22 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant