[krishika08]

Summary

RepoNeedle 1.2.0 was published to PyPI on 2026-11-12: wheel and sdist, uploaded by the release workflow. This documentation-only PR replaces the remaining pre-release wording ("upcoming", "PyPI publication pending", "install from source until 1.2.0 is published") with the released status.

No source code, tests, dependencies, configuration, version number, tag, Hugging Face Space or demo API changed. Only Markdown files changed: 26 lines in each direction.

Changes

Requested files

File	Change
README.md	See the list below.
CHANGELOG.md	Heading [1.2.0] — Unreleased (upcoming) → [1.2.0] — 2026-11-12. Removed the "has not yet been published" notice. All release notes are unchanged, including "does not change retrieval quality".
KNOWN_LIMITATIONS.md	The "Applies to" line now reads "Released 1.1.0 (PyPI, 2026-11-03) and 1.2.0 (PyPI, 2026-11-12)". No limitation or benchmark qualification changed.
docs/MCP_INTEGRATION.md	Status is now "Released in RepoNeedle 1.2.0 (PyPI, 2026-11-12)". The note that the PyPI command can't be resolved is replaced by "1.1.0 has no MCP server; the >=1.2.0 pin upgrades it". The from-clone commands remain as local development instructions. The "Not yet validated in a live Claude Code, Cursor, Cline or Windsurf session" limitation is unchanged.

README.md changes:

• Release status table header: 1.1.0 (PyPI, 2026-11-03) and 1.2.0 (PyPI, 2026-11-12).
• Text below the table: "install from source until 1.2.0 appears" is replaced by "both versions are on PyPI", with a link to the CHANGELOG migration notes.
• Quickstart: the "Before 1.2.0 is published" comment becomes "For local development". Both the PyPI and the clone commands are kept.
• Installation details table: the "before 1.2.0 is on PyPI" row is relabelled "From a clone, for development".
• Installation note: the "1.2.0 is upcoming…" note is replaced by "the >=1.2.0 pin upgrades 1.1.0, which has no MCP server, --json or --anchors".
• MCP section intro: "upcoming" and "until 1.2.0 is on PyPI" are removed. The live-client validation limitation is kept.
• Part E release status: "1.2.0 is published on PyPI (2026-11-12)"; 1.1.0 (2026-11-03) introduced change_impact; the default ranker is legacy in both.

Other user-facing status statements found by searching the repository

File	Change
CLAIMS_AND_EVIDENCE.md	"development branch that became 1.2.0 (upcoming; PyPI publication pending)" → "(published to PyPI on 2026-11-12)". The provenance clause is unchanged.
docs/BENCHMARK_CONFIGURATION.md	"1.2.0 (upcoming; PyPI publication pending) changed a default" → "1.2.0 (PyPI, 2026-11-12) changed a default".
docs/ROADMAP.md	The intro's status labels and the section heading Upcoming: … (PyPI publication pending) → Released: RepoNeedle 1.2.0 (PyPI, 2026-11-12).
docs/ANNOUNCEMENT.md	"from 1.2.0 (upcoming)" → "from 1.2.0"; "disabled by default on the current development branch" → "disabled by default from 1.2.0".
REPONEEDLE_V1_FINAL_DELIVERY.md	The banner on this historical record said "current release is 1.1.0; development branch planned for 1.2.0 (unreleased)". It now names 1.2.0 as the current release. The record itself is unchanged.

Intentionally unchanged

• Historical measurement provenance, for example "the pre-release 1.2.0 development branch of 2026-11-09, which produced identical rankings":

  • README Part A note;
  • CLAIMS_AND_EVIDENCE.md §ARB evidence;
  • KNOWN_LIMITATIONS.md §5;
  • CHANGELOG.md backward compatibility;
  • docs/BENCHMARK_CONFIGURATION.md §6–§8;
  • docs/ANNOUNCEMENT.md re-run notes;
  • the coverage measurement in docs/ROADMAP.md.

  These describe when and on which code measurements were made, not release status.

• reports/release_audit_1.2.0/RELEASE_AUDIT.md and the superseded PROPOSED_CHANGELOG_1.2.0.md are dated audit records of the pre-release state.

• docs/pypi_trusted_publishing.md uses "pending publisher", which is PyPI's term for a publisher registered before the project exists, not a release status.

• The Hugging Face Space and the demo api.py still bundle 1.1.0. The CHANGELOG states this, and they are out of scope here.

Checks

Check	Result
Repository search for pre-release status wording outside reports/ and research/ ("upcoming", "unreleased", "publication pending", "until 1.2", "before 1.2.0", "planned for 1.2", "installs 1.1.0", "current release is 1.1")	No matches remain
tests/test_documentation_consistency.py	19 passed
Full suite (Windows, Python 3.12)	506 passed, 7 skipped (file-symlink creation not permitted on this host)
Relative links and anchors in the 9 changed files, including the new CHANGELOG.md#migrating-from-11x	No new problems. Two broken links already on main are on lines this PR does not touch: KNOWN_LIMITATIONS.md → BENCHMARK_CONFIGURATION.md#research-integrity-notes (anchor not found), and a file:/// link in REPONEEDLE_V1_FINAL_DELIVERY.md
git diff --name-only	Only .md files

git diff --check reports trailing whitespace on line 3 of three files. Those are the existing two-space Markdown line breaks in the header blocks, kept as they were.

🤖 Generated with Claude Code