Skip to content

chore(main): release 0.8.0#88

Open
app-token-issuer-ops-platform[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cld-changesets
Open

chore(main): release 0.8.0#88
app-token-issuer-ops-platform[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cld-changesets

Conversation

@app-token-issuer-ops-platform

@app-token-issuer-ops-platform app-token-issuer-ops-platform Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.8.0 (2026-06-26)

⚠ BREAKING CHANGES

  • DeleteChainMetadataChangesetInput.ChainMetadataKeys, DeleteContractMetadataChangesetInput.ContractMetadataKeys, and DeleteAddressRefChangesetInput.AddressRefKeys — plus the matching operation Input fields — now hold concrete key structs instead of the framework interface. The DeleteAddressRefKey type previously exported from datastore/changesets/ is removed. In-Go callers should switch to JSON construction (no in-tree callers in chainlink-deployments today).

Features

  • add DeleteResourcesSeq and DeleteResourcesChangeset (#78) (f33c8f4)
  • add refactored set config changeset,sequences and ops (#90) (f5dde6f)
  • deploy custom topology mcms [CLD-2766] (#100) (b9638bc)
  • fund mcms pdas [CLD-2765] (#101) (c71b37c)
  • jd changesets (#103) (628cfb7)
  • JD changesets and operations (628cfb7)
  • mcms: add MCMS fire drill changeset [CLD-2764] (#97) (2530e9e)
  • mcms: add transfer-to-timelock changeset [CLD-2762] (#99) (0d52620)
  • new mcms deploy changeset (#89) (a0317ae)

Bug Fixes

  • make datastore delete inputs JSON-deserializable (#87) (68d4cda)
  • use opscontract.WriteOutput in set-config (#107) (e1a60bb)

This PR was generated with Release Please. See documentation.

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

Release impact (release-please)

Current version 0.7.1 (on main)
After merge no version bump (no release)

PR title: chore(main): release 0.8.0

This title will not trigger a semver bump when squash-merged to main. Use feat: for a minor release, or fix: / perf: / revert: for a patch release.

Conventional commit → bump

Intent PR title prefix Bump
Bug fix fix: patch
New feature feat: minor
Breaking change feat!: / fix!: or BREAKING CHANGE: / BREAKING-CHANGE: in description major
No release chore:, docs:, ci:, refactor:, etc. none

Update the PR title before merge if you need a different bump (squash commit message = PR title).

Preview is based on this PR title only. The release-please release PR may include other unreleased commits already on main.

@app-token-issuer-ops-platform app-token-issuer-ops-platform Bot force-pushed the release-please--branches--main--components--cld-changesets branch 4 times, most recently from f4c9012 to 7597883 Compare June 17, 2026 14:39
@app-token-issuer-ops-platform app-token-issuer-ops-platform Bot force-pushed the release-please--branches--main--components--cld-changesets branch 7 times, most recently from abdf0f6 to a41b90a Compare June 26, 2026 06:17
@app-token-issuer-ops-platform app-token-issuer-ops-platform Bot force-pushed the release-please--branches--main--components--cld-changesets branch from a41b90a to 7586742 Compare June 26, 2026 17:52
@cl-sonarqube-production

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

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.

0 participants