Skip to content

chore(release): v1.4.2rc1 - #500

Merged
gloryfromca merged 1 commit into
mainfrom
chore/release-1.4.2rc1
Oct 14, 2026
Merged

gloryfromca merged 1 commit into
mainfrom
chore/release-1.4.2rc1

Conversation

@gloryfromca

Copy link
Copy Markdown
Member

Summary

Cut 1.4.2rc1 so this cycle's index rework is exercised against a real PyPI
resolution before 1.4.2 goes out. The release pipeline's own smoke installs the
built wheel with --no-deps, so it cannot catch a resolution break on its own —
1.2.3 shipped broken that way.

What testers get to exercise:

Three files, all version number: pyproject.toml, docs/openapi.json,
uv.lock. docs/openapi.json moves with the version because
app.openapi()["info"]["version"] reads everos.__version__ from installed
package metadata, and make lint fails on a stale dump.

No CHANGELOG section: release.yml drafts a pre-release with a placeholder body
when the version has no ## [X.Y.Z] heading. The 1.4.2 section is written in the
stable release PR.

Testers must pass --pre — pip skips pre-releases by default and would
silently install 1.4.1 instead:

pip install --pre everos==1.4.2rc1

Area

  • Architecture method
  • Benchmark
  • Use case
  • Documentation
  • Developer experience
  • CI, build, or release

Verification

make ci                                       exit 0
  ruff check + ruff format --check + lint-imports + repo asset/file-size/
  deprecated-name/contributor-doc/datetime gates + openapi drift check
  unit        2681 passed, 4 skipped
  integration  186 passed, 7 skipped, 7 deselected
  package     built everos-1.4.2rc1 sdist + wheel, import smoke printed 1.4.2rc1

make docs-check                               exit 0
make check-openapi                            exit 0
scripts/check_commit_messages.py origin/main..HEAD   exit 0
scripts/check_pr_title.py                     exit 0   (title 25 chars; 32 after
                                                        the squash ` (#NNN)` suffix)

make check-cjk                                exit 1 — pre-existing: 10 hits in 7
  files (README badge URLs, use-cases/, a TUI demo), none touched by this diff.
  Advisory target, not wired into CI.

Soak evidence behind the #496 defaults in this release: three platforms
(macOS / Linux / Windows), idle and high-frequency-add, watching descriptors,
memory, disk and CPU. Descriptors converge on all three; disk is reclaimed on
compaction rather than accruing.

Checklist

  • I kept the change scoped to the relevant area.
  • I am opening this from a separate branch, not pushing directly to main.
  • I updated docs, examples, or setup notes when behavior changed.
  • I added or updated tests when the change affects behavior.
  • I did not commit secrets, .env files, dependency folders, or generated output.
  • Active relative links in Markdown files resolve.

Notes for Reviewers

The tag must be the literal PEP 440 form v1.4.2rc1 — release.yml compares it
to the pyproject.toml version as a string, and 1.4.2-rc1 would normalize to
1.4.2rc1 at build time and fail that guard.

After this merges, the publish still pauses on the release environment for a
manual approval before anything reaches PyPI.

🤖 Generated with Claude Code

Pre-release so this cycle's index rework — per-project primary keys
(#481), the quiesce drain (#487), the capped LanceDB caches and the
query embedding budget (#496) — is exercised against a real PyPI
resolution before 1.4.2 goes out. The release pipeline's own smoke
installs the built wheel with `--no-deps`, so it cannot catch a
resolution break on its own.

`docs/openapi.json` moves with the version: `app.openapi()["info"]
["version"]` reads `everos.__version__` (installed package metadata),
and `make lint` fails on a stale dump.

Testers must pass `--pre`; pip skips pre-releases by default and would
silently install 1.4.1 instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@gloryfromca
gloryfromca merged commit 2afcf37 into main Oct 14, 2026
11 checks passed
@gloryfromca
gloryfromca deleted the chore/release-1.4.2rc1 branch October 14, 2026 09:14
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