chore: realign pyproject.toml to published 1.2.3#14
Closed
luke-speechify wants to merge 11 commits into
Closed
Conversation
Added context7.json to the ignore list.
chore: add context7.json and update .fernignore
fix: update API URL in context7.json
- Add .github/workflows/release-please.yml combining compile + test +
release-please + publish into a single workflow.
- Add release-please-config.json (manifest mode, release-type python,
include-v-in-tag false to match existing tag style, extra-files for
client_wrapper.py).
- Add .release-please-manifest.json seeded with 1.2.3.
- Add an x-release-please-version marker comment to the X-Fern-SDK-Version
header in src/speechify/core/client_wrapper.py so the generic updater
can bump it on every release.
- Update .fernignore:
- keep .github/workflows/ci.yml so Fern does not recreate it after deletion
- add new release-please files and CHANGELOG.md
- add src/speechify/core/client_wrapper.py so the marker survives Fern
regeneration
- Delete .github/workflows/ci.yml.
ci: replace ci.yml with release-please workflow
The generated pyproject carried a partial PEP-621 `[project]` table
(name only, no version/dependencies) alongside the real `[tool.poetry]`
config. PEP-621 build frontends (uv, pip git installs) validate
`[project]` and fail ("project.version neither set nor in dynamic"), so
`pip install git+...` / uv source installs were broken (PyPI wheels were
unaffected). Drop the vestigial `[project]`/`[project.urls]` tables and
move the URLs under `[tool.poetry.urls]` so poetry-core fully owns the
metadata. `uv build` now produces sdist + wheel.
NOTE: hand-patch of a generated file; the durable fix is upstream in the
Fern python generator's pyproject emission.
fix(packaging): make the SDK installable from source [DRG-31]
The release-please manifest tracks 1.2.3 (the latest PyPI release) and src/speechify/core/client_wrapper.py also embeds 1.2.3 via the x-release-please-version marker, but pyproject.toml was bumped to 1.2.4 by a regen after PR #12's release-please PR was closed without publishing. Bring pyproject.toml back to 1.2.3 so release-please's source-of-truth (the manifest) is consistent with every other version reference in the repo. The next conventional commit will let release-please propose the correct next bump.
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
1 participant
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.
What
Bring
pyproject.tomlback to 1.2.3 so the release-please manifest, the embeddedX-Fern-SDK-Versionliteral insrc/speechify/core/client_wrapper.py, and the actually-published PyPI version (speechify-api==1.2.3) all agree.Why
After PR #11 landed the release-please-takeover config, an SDK regen pushed
pyproject.tomlto1.2.4and PR #12 (the auto-opened release-please release PR for 1.2.4) was closed without merging — so 1.2.4 was never published to PyPI. That left the repo in an inconsistent state:speechify-apilatest.release-please-manifest.jsonsrc/speechify/core/client_wrapper.py(x-release-please-version)pyproject.tomlRelease-please uses the manifest as its source-of-truth for "the last released version", and bumps everything from there. Leaving
pyproject.tomlat 1.2.4 would make release-please's next bump propose1.2.5while skipping a real 1.2.4 release that never happened. Realigning to 1.2.3 lets release-please cut a clean 1.2.4 (or whatever the next conventional commits warrant) on the next merge to master.Verification
No behavioral or dependency changes; only the version field.