Skip to content

Conversation

uozopio
Copy link
Contributor

@uozopio uozopio commented Jun 26, 2025

πŸš€ Production Release v0.3.0

This PR completes the release pipeline test by merging staging to main, which will trigger the automated release workflow.

βœ… Completed Phases:

  1. Feature Development: feat/release-pipeline-test β†’ develop (PR feat: add formatDate utility and complete test coverage for release pipeline testingΒ #14) βœ…
  2. Release Creation: release/v0.3.0 β†’ staging (PR release: v0.3.0Β #15) βœ…
  3. Production Deploy: staging β†’ main (This PR) πŸ”„

πŸ“‹ Changes Included:

  • ✨ Added formatDate utility function to core package
  • βœ… Complete test coverage for all packages and apps
  • πŸ› Fixed TypeScript compilation errors

πŸ€– Expected Automated Actions on Merge:

When this PR is merged to main, the release workflow will:

  1. Run npx auto shipit
  2. Bump version from 0.2.0 to 0.3.0
  3. Generate CHANGELOG.md entries
  4. Create git tag v0.3.0
  5. Publish GitHub release

πŸ“Š Test Results:

All tests passing (20 total tests across all packages)


Note: This is the final step in testing the complete release pipeline end-to-end.

Umutcan Γ–NER and others added 6 commits June 26, 2025 13:53
…tting

- Implement formatDate function that accepts string or Date object
- Returns ISO formatted date string
- Includes comprehensive tests for the new function
- Validates input and throws error for invalid dates
- Add missing test files for auth and database packages
- Fix test runner failures by ensuring all packages have test coverage
- Update test implementation to match actual module exports
- Add test files for cms, api, web, and app packages
- Ensure all packages have at least minimal test coverage
- Fix test runner failures across the monorepo
- Remove unused Content type import from cms test file
- Fix TypeScript compilation error in build process
feat: add formatDate utility and complete test coverage for release pipeline testing
Copy link

❌ PR Validation Failed

Please ensure your PR meets all requirements:

  1. Branch Naming: Follow conventions like feat/description, fix/issue-123
  2. PR Title: Use format <type>(<scope>): <subject> (e.g., feat(auth): add OAuth support)
  3. PR Size: Keep changes under 5000 lines and 100 files
  4. Breaking Changes: Document with "!" in title and description

See our Contributing Guide for details.

1 similar comment
Copy link

❌ PR Validation Failed

Please ensure your PR meets all requirements:

  1. Branch Naming: Follow conventions like feat/description, fix/issue-123
  2. PR Title: Use format <type>(<scope>): <subject> (e.g., feat(auth): add OAuth support)
  3. PR Size: Keep changes under 5000 lines and 100 files
  4. Breaking Changes: Document with "!" in title and description

See our Contributing Guide for details.

@uozopio uozopio requested a review from adminzopio June 26, 2025 11:14
adminzopio
adminzopio previously approved these changes Jun 26, 2025
@uozopio uozopio changed the title Release v0.3.0 to Production release: v0.3.0 Jun 26, 2025
Copy link

github-actions bot commented Jun 26, 2025

βœ… PR Size Check Passed

This PR changes 192 lines across 9 files.

Umutcan Γ–NER added 2 commits June 26, 2025 14:19
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@uozopio uozopio merged commit 96f2501 into main Jun 26, 2025
19 of 21 checks passed
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