Skip to content
This repository was archived by the owner on Sep 10, 2025. It is now read-only.

chore(main): release v0.13.0#316

Closed
bowlofarugula wants to merge 1 commit intomainfrom
release-please--branches--main--components--ftl
Closed

chore(main): release v0.13.0#316
bowlofarugula wants to merge 1 commit intomainfrom
release-please--branches--main--components--ftl

Conversation

@bowlofarugula
Copy link
Copy Markdown
Member

@bowlofarugula bowlofarugula commented Aug 23, 2025 •
edited by fastertools-gha bot
Loading

🚀 Release PR

This PR was generated by release-please.

0.13.0 (2025-08-25)

What's Changed

New Contributors

Full Changelog: v0.12.0...v0.13.0

⚠️ Do not manually edit this PR. Any manual changes will be overwritten by release-please.

To make changes, commit to main with conventional commit messages.

@bowlofarugula bowlofarugula force-pushed the release-please--branches--main--components--ftl branch from f286991 to 0219f0f Compare August 23, 2025 01:21
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Aug 23, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@bowlofarugula bowlofarugula force-pushed the release-please--branches--main--components--ftl branch from 0219f0f to 2834156 Compare August 23, 2025 01:31
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Aug 23, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@fastertools-gha fastertools-gha bot force-pushed the release-please--branches--main--components--ftl branch from 2834156 to 844eab8 Compare August 24, 2025 01:55
@fastertools-gha
Copy link
Copy Markdown
Contributor

fastertools-gha bot commented Aug 24, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@fastertools-gha fastertools-gha bot force-pushed the release-please--branches--main--components--ftl branch from 844eab8 to 6bec43e Compare August 24, 2025 02:03
@fastertools-gha
Copy link
Copy Markdown
Contributor

fastertools-gha bot commented Aug 24, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@fastertools-gha fastertools-gha bot force-pushed the release-please--branches--main--components--ftl branch from 6bec43e to 1d7b0ab Compare August 24, 2025 02:20
@fastertools-gha
Copy link
Copy Markdown
Contributor

fastertools-gha bot commented Aug 24, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@fastertools-gha fastertools-gha bot force-pushed the release-please--branches--main--components--ftl branch from 1d7b0ab to 0bace70 Compare August 25, 2025 00:10
@fastertools-gha
Copy link
Copy Markdown
Contributor

fastertools-gha bot commented Aug 25, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@fastertools-gha fastertools-gha bot force-pushed the release-please--branches--main--components--ftl branch from 0bace70 to 1769c27 Compare August 25, 2025 02:59
@fastertools-gha
Copy link
Copy Markdown
Contributor

fastertools-gha bot commented Aug 25, 2025

Release Validation Report

Check Status Description
✅ configuration Passed Release configuration files valid
⏭️ versions Skipped Version consistency across all files
✅ dependencies Passed Cross-package dependency alignment
✅ wasm Passed WASM runtime constraint compliance

ℹ️ Release PR Validation

Version consistency checks are skipped for release PRs as the versions are being updated.
This is expected behavior.

Recommendations

  • Ensure all version files are synchronized
  • Verify conventional commit messages are being used
  • Check that all package paths in release-please-config.json are correct
  • Review WASM dependencies for compatibility

@bowlofarugula
Copy link
Copy Markdown
Member Author

bowlofarugula commented Aug 25, 2025

Closing this separate release PR. The release process has been reconfigured to use unified PRs with proper Rust workspace dependency management. A new unified release PR will be created automatically.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending chore size/S

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@bowlofarugula