Archive v0.3.2 release task#116
Merged
Merged
Conversation
The v0.3.2 release is live on production (PR #115, tag v0.3.2, devops PR #278, ArgoCD sync, rollout clean). End-to-end DOCX import/export against `form.docx` works — the new S3-backed image pipeline is verified from upload through proxy render. Browser smoke test surfaced two preexisting DOCX importer bugs that were masked by lack of real-world test input: `w:val="0"` is treated as ON for bold/italic/strikethrough, and `tbl.getElementsByTagNameNS('w:gridCol')` is recursive and leaks nested-table column counts into the outer table. Both are import-only bugs (no server/schema/infra impact), so v0.3.2 is kept as released and the fixes will ship in v0.3.3. Follow-up task file will be added in a separate commit. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
📝 WalkthroughWalkthroughDocumentation task tracking files were updated to record completion of the v0.3.2 release cycle, including detailed release checklist execution logs, smoke test outcomes, and DOCX import/export work. Active task indices and archive counts were adjusted accordingly across multiple task documentation files. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/tasks/archive/2026/04/20260411-release-v0.3.2-todo.md`:
- Around line 117-123: The file contains conflicting version statements: one
corrected paragraph says the bump is v0.3.1 → v0.3.2, but other sections still
say v0.3.0 → v0.3.2 (notably the "scope" and "rollback risk" sections). Update
all occurrences of the old baseline to the single source-of-truth v0.3.1 →
v0.3.2 (search for the string "v0.3.0 → v0.3.2" and replace), and verify the
"scope" and "rollback risk" paragraphs reflect v0.3.1 → v0.3.2 and the note that
v0.3.1 was a routine image bump with no env var changes so rollback guidance
remains consistent.
In `@docs/tasks/README.md`:
- Line 21: The README row for "docx import export (2026-04-10)" is missing a
paired lessons file; create a paired lessons placeholder named
20260410-docx-import-export-lessons.md and add it to the active tasks, then
update the Lessons column in the README row (currently "-") to link to
20260410-docx-import-export-lessons.md so the entry reads like the other
non-trivial tasks with both a -todo and -lessons file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8f8161a9-1246-420f-9f99-7126b82fe6c2
📒 Files selected for processing (3)
docs/tasks/README.mddocs/tasks/archive/2026/04/20260411-release-v0.3.2-todo.mddocs/tasks/archive/README.md
Comment on lines
+117
to
+123
| > **Correction from earlier plan:** devops was at `v0.3.1`, not | ||
| > `v0.3.0` — the initial observation was based on a stale local | ||
| > clone of `devops/main`. The actual bump is therefore | ||
| > `v0.3.1 → v0.3.2`. v0.3.1 was a routine image bump (PR #276 by | ||
| > the user on 2026-04-05) with no env var changes — "no server | ||
| > deployment needed" meant no new env vars or infrastructure, not | ||
| > that the deployment was skipped. |
There was a problem hiding this comment.
Resolve remaining version-baseline contradictions in this same task record.
Good correction here, but the file still contains earlier v0.3.0 → v0.3.2 statements (scope and rollback risk) that now conflict with this section. Please align those sections to one source of truth to avoid operational confusion during rollback/reference.
Suggested doc fix
-3. **devops repo** — bump `k8s/wafflebase/deployment.yaml` from
- `v0.3.0` to `v0.3.2` (v0.3.1 was an intentional tag-only
- checkpoint) and wire the AWS credentials as env vars.
+3. **devops repo** — bump `k8s/wafflebase/deployment.yaml` from
+ `v0.3.1` to `v0.3.2` and wire the AWS credentials as env vars.
-3. **Image tag jump v0.3.0 → v0.3.2.** Rollback target is v0.3.0,
- not v0.3.1. If rollback is needed, revert the devops commit and
+3. **Image tag bump v0.3.1 → v0.3.2.** If rollback is needed, revert
+ the devops commit (or pin image back to v0.3.1), and
re-sync ArgoCD; no schema changes require a database rollback.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/tasks/archive/2026/04/20260411-release-v0.3.2-todo.md` around lines 117
- 123, The file contains conflicting version statements: one corrected paragraph
says the bump is v0.3.1 → v0.3.2, but other sections still say v0.3.0 → v0.3.2
(notably the "scope" and "rollback risk" sections). Update all occurrences of
the old baseline to the single source-of-truth v0.3.1 → v0.3.2 (search for the
string "v0.3.0 → v0.3.2" and replace), and verify the "scope" and "rollback
risk" paragraphs reflect v0.3.1 → v0.3.2 and the note that v0.3.1 was a routine
image bump with no env var changes so rollback guidance remains consistent.
|
|
||
| | Task | Todo | Lessons | | ||
| |---|---|---| | ||
| | docx import export (2026-04-10) | [20260410-docx-import-export-todo.md](./active/20260410-docx-import-export-todo.md) | - | |
There was a problem hiding this comment.
Add the paired lessons file entry for this non-trivial active task.
Given the task scope (docx import/export + release follow-ups), this should likely have a matching -lessons.md file (or an explicit planned placeholder) instead of - in the Lessons column.
Based on learnings: “Applies to docs/tasks/active/*-{todo,lessons}.md : For non-trivial tasks, use paired files in docs/tasks/active/: YYYYMMDD-<slug>-todo.md and YYYYMMDD-<slug>-lessons.md”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/tasks/README.md` at line 21, The README row for "docx import export
(2026-04-10)" is missing a paired lessons file; create a paired lessons
placeholder named 20260410-docx-import-export-lessons.md and add it to the
active tasks, then update the Lessons column in the README row (currently "-")
to link to 20260410-docx-import-export-lessons.md so the entry reads like the
other non-trivial tasks with both a -todo and -lessons file.
Contributor
Verification: verify:selfResult: ✅ PASS in 115.0s
Verification: verify:integrationResult: ✅ PASS |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
6 tasks
3 tasks
3 tasks
This was referenced May 21, 2026
4 tasks
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Marks the v0.3.2 release task as complete and moves it to
docs/tasks/archive/2026/04/. The release is fully live:yorkieteam/wafflebase:v0.3.2+:lateston Docker HubIMAGE_STORAGE_*env vars merged, ArgoCD synced, rollout clean
wafflebaseinap-northeast-2+ scopedIAM user
wafflebaseprovisionedEnd-to-end DOCX import/export against a real-world
form.docx(1.2 MB, 46 tables, inline images) works: the new S3-backed
image pipeline is verified from upload through proxy render.
Two import-only bugs found during smoke test (not blockers)
Keeping v0.3.2 as released. Follow-up fixes will ship in v0.3.3.
w:val="0"treated as ON for bold / italic / strikethrough—
docx-style-map.ts:21-23checks only element presence.form.docxcontains 509 + 509 + 513 such explicit "off"toggles, so most text renders with unintended strikethrough.
tbl.getElementsByTagNameNS('w:gridCol')is recursive andpicks up nested tables' grid columns. The importer's row
walk already uses direct-child traversal for
<w:tr>; thegridCollookup is an asymmetric survivor. Inform.docxthis inflates outer table column counts from e.g. 1 → 12
for the "별첨" tables, collapsing real columns to ~8% of
the content width.
Both are import-path only (no server / schema / infra impact).
Test plan
pnpm verify:fastpasses locally (pre-commit hook)pnpm verify:selfpasses via pre-push hookpnpm tasks:archivemoved the todo and regenerated bothdocs/tasks/README.mdanddocs/tasks/archive/README.md🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Documentation