Skip to content

blastdns: update packages - #3580

Merged
github-actions[bot] merged 4 commits into
mainfrom
package/blastdns
Oct 25, 2026
Merged

github-actions[bot] merged 4 commits into
mainfrom
package/blastdns

Conversation

@riseproject-dev

Copy link
Copy Markdown
Contributor

Automatically generated by the nightly check_versions.py run.

blastdns v1.9.1 -> v2.0.0, v2.0.1, v2.0.2

Every - version: entry added to docs/packages/blastdns.yaml is built by this PR's own build-blastdns.yml run; merging publishes the wheels.

@riseproject-dev
riseproject-dev Bot requested a review from luhenry October 22, 2026 11:58
riseproject-dev Bot and others added 3 commits October 23, 2026 07:49
Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
Upstream publishes no git tags, so the workflow pinned the single 1.9.1
release commit and checked it out for every version, then failed applying
patches/blastdns/<version> for versions without one. Map each version to
its own release commit (2.0.0, 2.0.1 and 2.0.2 each match their PyPI
sdist apart from maturin's injected readme line) and skip patching when a
version has no patch directory: 2.0.0 onwards already carries the AGPL
LICENSE the 1.9.1 patch backported.
A version missing from the ref map would check out the default branch and
build the wrong sources under that version number; compare the checkout's
pyproject.toml version with the requested one.
@github-actions
github-actions Bot marked this pull request as ready for review October 25, 2026 17:47
@github-actions
github-actions Bot merged commit 20eb1ed into main Oct 25, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant