Skip to content

chore(main): release github.com/altertable-ai/altertable-lakehouse-go 1.1.0 - #25

Merged
fvaleye merged 1 commit into
mainfrom
release-please--branches--main--components--github.com/altertable-ai/altertable-lakehouse-go
Oct 19, 2026
Merged

fvaleye merged 1 commit into
mainfrom
release-please--branches--main--components--github.com/altertable-ai/altertable-lakehouse-go

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.1.0 (2026-10-07)

Features


This PR was generated with Release Please. See documentation.

@albert20260301

Copy link
Copy Markdown
Contributor

@fvaleye Please do not merge this as a routine release yet. It continues the module-prefixed tag scheme (github.com/altertable-ai/altertable-lakehouse-go-v1.1.0), while go list -m -versions github.com/altertable-ai/altertable-lakehouse-go still cannot resolve the prior v1.0.0 release. The version/tag strategy needs the pending maintainer decision before another release is published.

@albert20260301

Copy link
Copy Markdown
Contributor

@fvaleye following up on the generated 1.1.0 release PR: it remains blocked because its module-prefixed tag scheme is not resolvable through the Go module proxy. Could you choose the canonical module tag and publishing strategy before this release is merged? I have not changed the generated branch.

@fvaleye
fvaleye merged commit f189453 into main Oct 19, 2026
2 checks passed
@fvaleye
fvaleye deleted the release-please--branches--main--components--github.com/altertable-ai/altertable-lakehouse-go branch October 19, 2026 10:52
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

2 participants