Skip to content

Merge dev to mainline — release 0.25.1 - #2758

Merged
antonsynd merged 5 commits into
mainlinefrom
dev
Nov 19, 2026
Merged

antonsynd merged 5 commits into
mainlinefrom
dev

Conversation

@antonsynd

Copy link
Copy Markdown
Owner

Release 0.25.1, promoting dev @ 7c104af to mainline at the owner's request (2026-11-19: "use Python-2.0 and cut 0.25.1").

Merging this tags v0.25.1 automatically and dispatches the release. The NuGet push uses --skip-duplicate.


Generated by Claude Code

claude and others added 5 commits November 19, 2026 18:50
The v0.25.0 release's NuGet push stopped at SharpyLang.Core with HTTP 400:
nuget.org refuses a licence expression naming an SPDX id that is not
OSI-approved or FSF-free, and PSF-2.0 is not. Stdlib and sharpyc carried
the same expression and were never pushed. Owner ruling 2026-11-19: use
Python-2.0, the OSI-approved SPDX id for the CPython licence. Core, Stdlib
and Cli now read (Apache-2.0 OR MIT) AND Python-2.0. Refs #2602.

build_tools/tests/test_package_licenses.py runs the server's check on
every change: every <PackageLicenseExpression> under src/ and in
Directory.Build.props names only ids in the accepted set, with a
positive control that the four packaged expressions are found.

Mutation: Core back to PSF-2.0 -> test_every_licence_id_is_one_nuget_accepts
red (names ['PSF-2.0']); restored -> 3 passed. Packing Core (Release,
serialized wrapper): no NU5124/NU5125; the nuspec license expression is
(Apache-2.0 OR MIT) AND Python-2.0.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LGMKZYfGwj3H3WNmGpXFFS
Patch release per owner ruling 2026-11-19: republish the NuGet packages
that nuget.org refused at 0.25.0 (licence id PSF-2.0, now Python-2.0).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LGMKZYfGwj3H3WNmGpXFFS
Independent review of 424f0ac (merge; two low findings, one nit):
- the expression regex now admits attributes (Condition=...);
- the scan covers every *.csproj, *.props and *.targets outside
  bin/obj/node_modules/.git/.venv, not only src/ and Directory.Build.props;
- a <PackageLicenseFile> anywhere fails, since it bypasses the check;
- the three csproj comments name the CPython licence (SPDX Python-2.0).

Mutations: a benchmarks/ .props with an attributed PSF-2.0 expression ->
test_every_licence_id_is_one_nuget_accepts red; a .targets setting
PackageLicenseFile -> test_no_project_licenses_by_file red; both removed
-> 4 passed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LGMKZYfGwj3H3WNmGpXFFS
build: name the CPython licence Python-2.0 so nuget.org accepts it

Copy link
Copy Markdown
Owner Author

The benchmark check is red for a reason outside this PR's changes. The allocation gate puts two compiler benchmarks just over its 10% threshold:

run code Compile_Classes Compile_LargeFunctions
PR run, #2755 0.25.0 (5bb23cba4) within 10% (OK) within 10% (OK)
mainline push 0.25.0 (45829650b) +10.6% +10.6%
this PR 0.25.1 (7c104af80) +10.8% +10.8%

Since 0.25.0, dev has gained only csproj licence metadata and the version number (#2756, #2757), and neither touches the compiler. The same 0.25.0 code passed the gate on one run and failed it on the next, so allocation drift over the 0.25 cycle has left these two benchmarks sitting on the threshold. Refreshing benchmarks/allocation-baseline.json (last set in #2550) is a deliberate owner decision, so I've asked the owner how to proceed instead of merging over the red check.


Generated by Claude Code

@antonsynd
antonsynd merged commit 0467728 into mainline Nov 19, 2026
43 of 44 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.

2 participants