-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Update blueprints to v8.7.3 #27739
Comments
I can release new versions for Ionic, Micronaut, Quarkus, and React Native if they're not already released. Is that enough to announce the 8.7.3 release? |
@mraible I've released migrate blueprint. Native blueprint will need more work. And I am finishing the dotnetcore upgrade, but don’t need to wait for them. We should wait 1 at most 2 days for blueprints to be updated before a release announcement. |
Current status:
|
React Native v5.1.0 has been released. I'll add bug bounties for Micronaut and Quarkus. |
I added updated blueprints to the release notes in jhipster/jhipster.github.io@ea78a8f. |
Micronaut v3.5.0 is now available! |
Quarkus v3.3.0 has shipped! |
Native v2.5.0 is released. |
.Net Core will need to wait for next version: #27764 |
This issue is done. |
Excellent! Is there an issue for the Node blueprint? |
|
I've updated the release notes for 8.7.3 in jhipster/jhipster.github.io#1406. It contains a list of updated blueprints and a note about .NET Core and Node. Here's a preview. I can continue with the 8.7.3 release steps if y'all think this looks good. |
@DanielFran bug bounty claimed https://opencollective.com/generator-jhipster/expenses/228474 |
@mshima Approved. |
Overview of the feature request
Update blueprints to v8.7.3.
generator-jhipster-nodejsNeeds workjhipster-dotnetcore: Bump generator-jhipster from 8.5.0 to 8.7.3 jhipster-dotnetcore#1520blocked on .Net blueprint cannot be released due to modularization specifics. #27764Motivation for or Use Case
Related issues or PR
The text was updated successfully, but these errors were encountered: