Merged
Conversation
Minor documentation issues found: - README permissions table missing scripting permission - "What We Don't Request" section needs update for scripting scope
Update documentation to reflect scripting permission added in v0.12.2 for DLP extension compatibility. Scripting is used only to send postMessage navigation to Zendesk's SPA. - Add scripting to permissions table in README - Add scripting to permissions table in PRIVACY.md - Update "What We Don't Request" to clarify scripting scope
Phase 5 verified: - 4/4 success criteria verified - STORE-01, STORE-02, STORE-04, STORE-05 requirements complete - VERIFICATION.md created with full goal-backward analysis
Phase 06: CI/CD & Automation - Release triggering decisions documented - Changelog format and version strategy captured - Artifact handling specifications defined
Phase 6: CI/CD & Automation - Standard stack: release-please v4 for version/changelog automation - Architecture: two-workflow pattern (release-please + tag-triggered release) - Keep a Changelog mapping via changelog-sections config - Pitfalls documented (GITHUB_TOKEN, version sync, pre-releases)
Phase 06: CI/CD & Automation - 2 plan(s) in 1 wave(s) - 2 parallel, 0 sequential - Ready for execution
- Plan 01: Document CICD-01/CICD-02 pre-satisfaction by Phase 4 ci.yml - Plan 01: Add ci.yml to context section - Plan 02: Add pre-condition noting ci.yml exists from Phase 4 - Plan 02: Add verification step for consistent Node 20 usage - Both: Ensure master branch references (not main)
- Add lint, test, build jobs before release job - Release job now requires all CI jobs to pass (needs: [lint, test, build]) - Add prerelease detection via contains(github.ref, '-') - Standardize Node version to 20 (matching ci.yml) - Renamed workflow from "Build release zip" to "Release"
- release-please-config.json with Keep a Changelog section mapping - .release-please-manifest.json tracking current version 0.12.3 - Uses node release-type for package.json version bumps
- Triggers on push to master branch - Uses googleapis/release-please-action@v4 - References config and manifest files for version tracking
- Document Conventional Commits format - Add type mapping table for changelog generation - Include examples of feat, fix, and breaking changes
Tasks completed: 2/2 - Enhance release workflow with CI gate - Create CLAUDE.md with commit conventions SUMMARY: .planning/phases/06-cicd-automation/06-02-SUMMARY.md
Tasks completed: 2/2 - Task 1: Create release-please configuration files - Task 2: Create release-please workflow SUMMARY: .planning/phases/06-cicd-automation/06-01-SUMMARY.md
Phase 6 verified and complete. All must-haves achieved: - CI runs on PRs and push to master - Release-please creates automated release PRs - Release workflow gates on lint/test/build - Changelog generated from conventional commits - CLAUDE.md documents commit conventions MILESTONE COMPLETE: QuickTab Modernization v1 - 6 phases, 23 plans, 68 minutes total
- Fix repository URLs in STORE-METADATA.md (zendesklabs → justcarlson) - Add null check for extension ID extraction in e2e/fixtures.ts - Replace non-null assertions with optional chaining in tests (per Biome) - Add @ts-expect-error for fake-browser mock type mismatches
- Remove resolved debug files (extension-slowness, zendesk-tab-closing) - Add v1 milestone audit report and integration report
Archived: - milestones/v1.0-ROADMAP.md - milestones/v1.0-REQUIREMENTS.md - milestones/v1.0-MILESTONE-AUDIT.md Deleted (fresh for next milestone): - ROADMAP.md - REQUIREMENTS.md Updated: - MILESTONES.md (new entry) - PROJECT.md (requirements → Validated) - STATE.md (reset for next milestone) Tagged: v1.0
6 requirements across 2 categories: - Version Sync (3): fix package.json, release-please workflow, artifact naming - Chrome Web Store (3): submit, address feedback, publish
Phases: 7. Version Sync: VER-01, VER-02, VER-03 8. Chrome Web Store: CWS-01, CWS-02, CWS-03 All milestone requirements mapped to phases.
Phase 7: Version Sync - Documented version mismatch between package.json (0.12.3) and GitHub release (v1.0) - Identified last-release-sha as critical config option for sync - Catalogued pitfalls for version file coordination - Provided code examples for all three files needing updates
Phase 07: Version Sync - 1 plan in 1 wave - 1 parallel, 0 sequential - Ready for execution
- Update package.json version from 0.12.3 to 1.0.1 - Update .release-please-manifest.json to 1.0.1 - Add last-release-sha pointing to v1.0 tag commit
Tasks completed: 2/2 - Update version files to 1.0.1 - Verify build produces correctly versioned artifact SUMMARY: .planning/phases/07-version-sync/07-01-SUMMARY.md
Phase 7 verified: - VER-01: package.json updated to 1.0.1 - VER-02: release-please configured correctly - VER-03: Build produces quicktab-v1.0.1-chrome.zip
Phase 08: Chrome Web Store - Implementation decisions documented - Phase boundary established
Phase 8: Chrome Web Store - Document store listing requirements (icons, screenshots, promo images) - Catalog permission justification best practices - Identify common rejection pitfalls (Purple Potassium, Purple Lithium) - Verify existing assets meet CWS requirements
Phase 08: Chrome Web Store - 2 plan(s) in 2 wave(s) - Wave 1: 08-01 (autonomous, prepare assets) - Wave 2: 08-02 (checkpoints, submit and verify) - Ready for execution
- Complete store listing with title, summary, description - Permission justifications for all 5 permissions - Privacy policy and support URLs - Asset checklist for submission
Tasks completed: 2/2 - Create Store Listing Content - Build and Verify Extension Package SUMMARY: .planning/phases/08-chrome-web-store/08-01-SUMMARY.md
Extension published to Chrome Web Store: - ID: nmdffjdpeginhmabpeikjimggmnoojjp - Version: 1.0.1 - Category: Workflow & Planning v1.0.1 milestone complete.
Archived: - milestones/v1.0.1-ROADMAP.md - milestones/v1.0.1-REQUIREMENTS.md - milestones/v1.0.1-MILESTONE-AUDIT.md Deleted (fresh for next milestone): - ROADMAP.md - REQUIREMENTS.md Updated: - MILESTONES.md (new entry) - PROJECT.md (requirements → Validated) - STATE.md (reset for next milestone) Tagged: v1.0.1
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
Phases
Key Changes
Chrome Web Store
Test plan