Skip to content

build(web): version 1-to-1 with mongospecs (0.2.0); ci: one job for docs-only changes - #11

Merged
jaykv merged 2 commits into
mainfrom
release/web-0.2.0
Oct 13, 2026
Merged

jaykv merged 2 commits into
mainfrom
release/web-0.2.0

Conversation

@jaykv

@jaykv jaykv commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

mongospecs-web's first release is 0.2.0, matching mongospecs, and the two are released together from now on. Updates the package version, __version__, the changelog, the release notes in CONTRIBUTING and the plan (A42).

🤖 Generated with Claude Code

Summary by Sourcery

Align mongospecs-web with mongospecs version 0.2.0 and streamline CI handling for documentation-only changes.

Enhancements:

  • Align mongospecs-web versioning with mongospecs at 0.2.0 and establish synchronized releases.
  • Run documentation checks for documentation-only changes while keeping the main CI pipeline focused on code changes.

CI:

  • Add a dedicated documentation workflow that builds the site and executes its examples on relevant pull requests and main-branch changes.
  • Update documentation deployment to publish through MkDocs after successful checks.

Documentation:

  • Update release guidance, changelog, package status, and project planning to reflect synchronized package versioning.

…t 0.2.0

The two packages now always carry the same version and are released
together. Recorded as A42, superseding A12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sourcery-ai

sourcery-ai Bot commented Oct 13, 2026

Copy link
Copy Markdown

Sorry @jaykv, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 6 days and 2 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: d580dbfb-142a-47af-b7e2-cf48a81c72dc
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai

sourcery-ai Bot commented Oct 13, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release synchronizes mongospecs-web with mongospecs at version 0.2.0 across package metadata, runtime reporting, documentation, and the lockfile, while documenting the required sequential release process and recording the policy change in the project plan.

File-Level Changes

Change Details Files
Aligned mongospecs-web package and runtime versions with mongospecs at 0.2.0.
  • Bumped the package metadata and exported version.
  • Updated the README release status and changelog entry to explain the synchronized first release.
  • Regenerated the lockfile for the version change.
packages/mongospecs-web/pyproject.toml
packages/mongospecs-web/src/mongospecs_web/__init__.py
packages/mongospecs-web/README.md
CHANGELOG.md
uv.lock
Documented and configured coordinated publishing of both packages.
  • Updated publish tag comments and release guidance to use 0.2.0 for both packages.
  • Documented that mongospecs must be published before mongospecs-web because of the dependency.
  • Recorded the decision as plan item A42, superseding the prior independent versioning plan.
.github/workflows/python-publish.yaml
CONTRIBUTING.md
claudedocs/v2-plan.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

A change that touches only Markdown, docs/ or mkdocs.yaml no longer
starts the twelve-job CI pipeline. The Docs workflow checks it with one
job that builds the site strictly and runs the examples the pages
contain, and still deploys from main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jaykv jaykv changed the title build(web): version mongospecs-web 1-to-1 with mongospecs (0.2.0) build(web): version 1-to-1 with mongospecs (0.2.0); ci: one job for docs-only changes Oct 13, 2026
@jaykv
jaykv merged commit bb0645a into main Oct 13, 2026
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