Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(very_good_flutter_plugin): update brick to Mason 0.1.0-dev.52 #52

Merged
merged 2 commits into from
Feb 26, 2024
Merged

chore(very_good_flutter_plugin): update brick to Mason 0.1.0-dev.52 #52

merged 2 commits into from
Feb 26, 2024

Conversation

alestiago
Copy link
Contributor

Description

Related to #38

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@alestiago alestiago added chore Changes that don't modify source code or tests product: very_good_flutter_plugin Changes that affect the Very Good Flutter Plugin template. labels Feb 26, 2024
@alestiago alestiago self-assigned this Feb 26, 2024
@alestiago alestiago merged commit b646f45 into main Feb 26, 2024
15 checks passed
@alestiago alestiago deleted the alestiago/update-flutter-plugin-mason-env branch February 26, 2024 12:12
@alestiago alestiago changed the title chore(very_good_flutter_plugin): update bricks to Mason 0.1.0-dev.52 chore(very_good_flutter_plugin): update brick to Mason 0.1.0-dev.52 Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@alestiago alestiago

Labels
chore Changes that don't modify source code or tests product: very_good_flutter_plugin Changes that affect the Very Good Flutter Plugin template.
Projects
VGV Open Source 🦄 🧙🌟
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@alestiago