Skip to content

chore(main): release instro-daq-mcc 1.1.0 - #427

Open
nominal-bot wants to merge 1 commit into
mainfrom
release-please--branches--main--components--instro-daq-mcc
Open

chore(main): release instro-daq-mcc 1.1.0#427
nominal-bot wants to merge 1 commit into
mainfrom
release-please--branches--main--components--instro-daq-mcc

Conversation

@nominal-bot

@nominal-bot nominal-bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.1.0 (2026-08-26)

Features

  • mcc: typed channel support for mcc daqs (#403) (df59d2f)

This PR was generated with Release Please. See documentation.

@claude

claude Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Claude finished @nominal-bot's task in 47s —— View job


Review

Automated release-please PR — no hand-written code to review. All three files are mechanical version bookkeeping and stay in sync:

  • .github/release-please-manifest.json: packages/instro-daq-mcc bumped 1.0.01.1.0
  • packages/instro-daq-mcc/pyproject.toml: version bumped to match
  • packages/instro-daq-mcc/CHANGELOG.md: new entry correctly attributes the bump to the sole feature commit (feat(mcc): typed channel support for mcc daqs #403, df59d2f), which used the proper feat(mcc): Conventional Commit prefix

No driver code, tests, or docs are touched, so the usual AGENTS.md driver/API/docs-sync checks don't apply here. Nothing to flag.

  • Gather context (PR is an automated release-please version bump for instro-daq-mcc)
  • Review changed files against repo conventions
  • Post findings

@greptile-apps

greptile-apps Bot commented Aug 24, 2026

Copy link
Copy Markdown

Greptile Summary

This release PR advances instro-daq-mcc from 1.0.0 to 1.1.0 for typed MCC DAQ channel support.

  • Updates the Release Please manifest and Python package metadata to version 1.1.0.
  • Adds the generated 1.1.0 changelog entry.

Confidence Score: 5/5

The PR appears safe to merge because its release metadata is internally consistent and follows the repository’s functioning release pattern.

The manifest, changelog, and package metadata consistently identify version 1.1.0, and no blocking or independently actionable issue remains.

Important Files Changed

Filename Overview
.github/release-please-manifest.json Advances the MCC package’s Release Please version to 1.1.0, consistent with the package metadata and changelog.
packages/instro-daq-mcc/CHANGELOG.md Documents the 1.1.0 release and its typed-channel feature with matching comparison, issue, and commit links.
packages/instro-daq-mcc/pyproject.toml Advances the published Python package version to 1.1.0 in line with the established release workflow.

Reviews (1): Last reviewed commit: "chore(main): release instro-daq-mcc 1.1...." | Re-trigger Greptile

@nominal-bot
nominal-bot force-pushed the release-please--branches--main--components--instro-daq-mcc branch from 54f1de7 to 8849a1e Compare August 25, 2026 19:53
@nominal-bot
nominal-bot force-pushed the release-please--branches--main--components--instro-daq-mcc branch from 8849a1e to e9f5d2b Compare August 26, 2026 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant