Repository navigation
release: prepare 2.0 (version, NEWS, plugin, version source, skill completeness) - #103
Merged
Merged
Conversation
- Bump version to 1.3 (fz/__init__.py), README badge, Claude Code plugin manifests 1.2.0 -> 1.3.0 (plugin.json, marketplace.json). - NEWS.md: "Unreleased" becomes "Version 1.3 (2026-11-06)", headed by a notice that the release contains backward-incompatible behavior changes and security/correctness fixes; a fresh empty "Unreleased" is opened. - Single version source: manifest.json (fz_version, RO-Crate fz entity) and fz.config's summary read the never-stamped fz/_version.py and reported "1.0"; they now read fz.__version__. tests/test_manifest.py checks it. - release.yml runs scripts/stamp_version.py before building the wheels and the sdist (no workflow ran it); fz/_version.py re-stamped; scripts/README.md and CLAUDE.md describe the actual behavior. - Skill (skills/fz/): install hint >= 1.3 with the 1.3 highlights; fix the stale claim that a model without "delim" reads only $(x); document the configuration/installer/discovery helpers exported in fz.__all__, the fz input/compile/output/list subcommands and model key aliases. - tests/test_skill_static.py: completeness checks (every fz.__all__ name and every top-level fz subcommand is mentioned in the skill). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RjXvVRjM6aMvKvvSFoxpZ6
The release contains backward-incompatible behavior changes (Python 3.8 dropped, cache key, default delimiters, timeouts, sh:// path resolution, fz list JSON), so it takes a major version number. - fz/__init__.py 2.0, README badge, plugin manifests 2.0.0. - NEWS.md: "Version 2.0", header states the major bump. - Skill: install hint funz-fz>=2.0, "fz >= 2.0" for default delimiters. - fz/_version.py re-stamped; scripts/README.md example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RjXvVRjM6aMvKvvSFoxpZ6
This was referenced Nov 6, 2026
yannrichet
pushed a commit
that referenced
this pull request
Nov 6, 2026
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.
Pull Request
Description
Prepares the 2.0 release, following the same procedure as the 1.2 preparation (
2a4c58a). The release is numbered 2.0 rather than 1.3 because it contains backward-incompatible behavior changes (listed inNEWS.md, "Upgrading from 1.2"). This PR also fixes a traceability defect found along the way (manifest.jsonrecordedfz_version: "1.0") and completes the agent skill.The tag and the GitHub release are not created by this PR. The branch name still says
1-3for historical reasons.Related Issues
Relates to #101 (warning on default delimiters, handled in a dedicated PR)
Relates to #102 (
release.ymlbuild matrix, not addressed here, apart from the stamping step)Type of Change
manifest.json/fz.configreported version 1.0)scripts/README.md, CLAUDE.md)Changes Made
fz/__init__.py1.2 → 2.0 (pyproject.tomlreads it dynamically); README badge; plugin manifests.claude-plugin/plugin.jsonandmarketplace.json1.2.0 → 2.0.0.sh://results, injection). A new empty "Unreleased" section is opened. The date is to be adjusted to the actual tag date.fz/manifest.py(fz_version, and the RO-Cratefzentity) andfz/config.py(get_summary()['version']) readfz/_version.py. No workflow ever stamped that file, so it held"1.0". Both now readfz.__version__.tests/test_manifest.pychecksfz_version == fz.__version__.release.ymlrunsscripts/stamp_version.pybefore building the wheels and the sdist.fz/_version.pyis re-stamped.scripts/README.mddescribed CI integrations that did not exist (ci.yml,stamp-version.yml); it is corrected, and so is CLAUDE.md.skills/fz/), completeness review:SKILL.md: install hintfunz-fz>=2.0, with the release highlights and the cache invalidation.reference.md, incorrect claim fixed: "a model withoutdelimreads only$(x);${name}is then NOT a variable" contradictedDEFAULT_VAR_DELIM = "(){}".reference.md, additions: helpers exported infz.__all__that were undocumented (set_log_level,get_log_level,get_config,print_config,get_interpreter,install_model/uninstall_model/list_installed_models,install_algorithm/uninstall_algorithm,list_models,discover_funz_servers); thefz input/fz compile/fz output/fz listsubcommands; model key aliases (var_prefix,formula_prefix,comment_line, ...).tests/test_skill_static.py: two completeness tests. Everyfz.__all__name and every top-levelfzsubcommand must appear in the skill. Both tests fail on the previous skill (12 missing names, plusfz input) and pass after this PR.Testing Performed
Automated Tests
Local run of the first commit (Linux, Python 3.13,
ci.yml--ignorelist):The 5 failures are pre-existing and environmental: they fail identically on
main(17f65e2) in the same container.test_fzi_with_permission_denied,test_install_model_with_permission_error,test_fzc_with_readonly_output_directory: tests run as root (uid 0), so file permissions are not enforced.test_evaluate_yq_scalar,test_evaluate_yq_prefix_detection_and_stripping: the installedyqis not the expected implementation (yq --version→0.0.0).After the rename to 2.0:
test_skill_static,test_manifest,test_readme_structure,test_project_metadataandtest_python_version_supportpass (24 tests).fz --version→fz 2.0;fz.get_config().get_summary()['version']→2.0. CI on the first commit was fully green.Manual Testing
Breaking Changes
This PR itself breaks nothing. The release it prepares does (listed in
NEWS.md, "Upgrading from 1.2"), hence 2.0.Additional Notes
Remaining before the tag:
NEWS.mdif the tag is not created on 2026-11-06.fz/_version.pyis stamped with the parent commit;release.ymlre-stamps it at build time.Generated by Claude Code
🤖 Generated with Claude Code
https://claude.ai/code/session_01RjXvVRjM6aMvKvvSFoxpZ6