Add blog post for Metalhead release v0.8 #160
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Bump on this if it's GTG? |
|
would be nice to add a couple of code examples |
I avoided this deliberately. There have been issues in the past with old syntax lying around in blog posts not being updated causing errors for new users, which is a pain point for onboarding. Thus redirecting users to the docs is the best solution as that can be kept updated without much hassle in case the library changes something. |
ToucheSir
approved these changes
Jun 11, 2023
Co-authored-by: Brian Chen <[email protected]>
|
Bump on merge if it's okay? |
|
Is it okay for me to link this on my social media now? I do want to let people know that there's been significant improvements they should be using 😅 |
|
Absolutely, go for it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Metalhead v0.8 is now tagged, I thought this would be a good explainer on a lot of the work that's happened in between v0.7 and v0.8.
cc @darsnack @ToucheSir for comments 😁