[dependabot]

Bumps github.com/matdev83/go-llm-interactive-proxy from 0.1.0-rc.1 to 0.1.0.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[matdev83]

Closing this as an incomplete baseline move, not as a bad version.

The repository pins the root and ACP host contracts at the same released version (README "Pinned host contract baseline", TestReleaseMetadata_AgreesWithThePinnedModuleBaseline, and TestPackageArchive's host_contract_root_version == host_contract_acp_version assertion). This PR moves only the root module, so it leaves connector-support/acp at v0.1.0-rc.1 and fails those guards; it also does not update the README table that has to name the same version.

A paired bump is not possible today: the module proxy has github.com/matdev83/go-llm-interactive-proxy/connector-support/acp at v0.1.0-rc.1 only - there is no v0.1.0 tag for the ACP module.

There is a second reason not to rush the root module to v0.1.0: that is the host release this repository records as unable to parse the v2 credential manifest (release.yaml host_certification_reason), so the module baseline should move together with a v2-capable host release and its re-certification, not ahead of it.

When connector-support/acp publishes a matching tag, the coordinated change is: both go.mod pins, README table, and the certification/evidence update - one reviewed change. Reopen or recreate then.