Skip to content

refactor(manifest)!: name manifest builder constructor explicitly - #2314

Merged
zeroshade merged 6 commits into
apache:mainfrom
fallintoplace:refactor/manifest-builder-constructor-upstream-20261024
Oct 26, 2026
Merged

zeroshade merged 6 commits into
apache:mainfrom
fallintoplace:refactor/manifest-builder-constructor-upstream-20261024

Conversation

@fallintoplace

Copy link
Copy Markdown
Contributor

What

  • Rename NewManifestFile to NewManifestBuilder.

Why

  • This function returns a ManifestBuilder.

Implementation

  • Rename the constructor and update in-repo call sites.

Refs #2062.

@fallintoplace
fallintoplace marked this pull request as ready for review October 24, 2026 11:34
Rename NewManifestFile to NewManifestBuilder to match the returned type and other public builder constructors.

Signed-off-by: Minh Vu <vuhoangminh97@gmail.com>
@fallintoplace
fallintoplace force-pushed the refactor/manifest-builder-constructor-upstream-20261024 branch from 55c3104 to afb7316 Compare October 25, 2026 11:05
fallintoplace and others added 5 commits October 25, 2026 12:32
…am-20261024

Restore the NewManifestBuilder compatibility note from 39f9e4d dropped by the release-notes sync.
…am-20261024

Take main's releases.md; the compatibility note for this change lands in a follow-up release-notes PR so the pre-v1 renames can merge in parallel.

@zeroshade zeroshade left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Straightforward rename: the function returns a *ManifestBuilder, and every in-repo caller is updated with no NewManifestFile references left. I pushed a merge of main (3452cbc); go vet ./... (including -tags integration) and the root and ./table/... tests pass. The compatibility note for this change (dropped by the "sync release notes with main" commit) will land in a single follow-up release-notes PR covering this batch of pre-v1 renames, so these can merge in parallel without releases.md conflicts. LGTM.

@zeroshade
zeroshade merged commit fc6f3d9 into apache:main Oct 26, 2026
16 checks passed
zeroshade added a commit to fallintoplace/iceberg-go that referenced this pull request Oct 26, 2026
Resolve the test overlaps with the renames already on main (apache#2308, apache#2314, apache#2317, apache#2319): each conflict hunk keeps this PR's sequence-number names with main's other renames applied.
zeroshade added a commit to zeroshade/iceberg-go that referenced this pull request Oct 28, 2026
…g changes

Add release notes for the rename batch (apache#2308, apache#2314, apache#2315, apache#2316, apache#2317,
apache#2319, apache#2322, apache#2323) and for apache#2067, apache#2290, apache#2294, apache#2307, apache#2310 and apache#2313.
Remove stray blank lines inside the compatibility-notes list.
zeroshade added a commit that referenced this pull request Oct 28, 2026
docs(release): add compatibility notes for pre-v1 renames and breaking changes

Add release notes for the rename batch (#2308, #2314, #2315, #2316, #2317,
#2319, #2322, #2323) and for #2067, #2290, #2294, #2307, #2310 and #2313.
Remove stray blank lines inside the compatibility-notes list.
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.

2 participants