Conversation
KyleJune
pushed a commit
that referenced
this pull request
Jan 12, 2026
# [0.2.0](0.1.2...0.2.0) (2026-01-12) ### Bug Fixes * Move provider in shared layout in tanstack template ([afb1f24](afb1f24)) * Normalize ignorePaths for dev server ([c2bde40](c2bde40)) ### Features * Add ignorePaths build configuration option ([e6009f3](e6009f3)) * Return json for not found urls with file extensions ([29b0318](29b0318)) * Update changelog and test semantic release ([#64](#64)) ([9289fe1](9289fe1)) * Use cbor2 for all server state serialization instead of SuperJSON ([ff57ee7](ff57ee7))
|
🎉 This PR is included in version 0.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
I didn't follow semantic release pattern for my last PR. I did a bunch of changes in 1 PR and tried merge commit because I thought semantic release would include all those commits in the changelog and do a release. It did not.
You can see info about the failure here:
https://github.com/udibo/juniper/actions/runs/20910029203/job/60071111718
I marked this as a feat so that I can see what happens when a feat is squash merged. If it doesn't automatically release 0.2.0, I will do it manually.