Skip to content

chore: release 0.7.0 🚀 #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 17, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 9, 2025

🤖 I have created a release beep boop

0.7.0 (2025-04-16)

Features

  • Type checking for all APIs and rules (#103) (809ea4c)

Bug Fixes

  • Set use-baseline to 'warn' in recommended config (#110) (2152e9d), closes #80

This PR was generated with Release Please. See documentation.

@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Apr 9, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main--components--css branch from 5587a4b to 017bc4c Compare April 11, 2025 14:28
@github-actions github-actions bot changed the title chore: release 0.6.1 🚀 chore: release 0.7.0 🚀 Apr 13, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main--components--css branch 2 times, most recently from 970e931 to 0a4fda5 Compare April 15, 2025 08:02
@github-actions github-actions bot force-pushed the release-please--branches--main--components--css branch from 0a4fda5 to 7ab70b1 Compare April 16, 2025 08:02
@mdjermanovic mdjermanovic merged commit fa391df into main Apr 17, 2025
3 checks passed
@mdjermanovic mdjermanovic deleted the release-please--branches--main--components--css branch April 17, 2025 21:08
@github-project-automation github-project-automation bot moved this from Needs Triage to Complete in Triage Apr 17, 2025
Copy link
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Complete
Development

Successfully merging this pull request may close these issues.

Rule Change: require-baseline might need to default to a warning
1 participant