Repository navigation
chore: fix bad merge commit for v11.14.0 - #7715
aloisklink merged 2 commits into
Conversation
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/11.15.0 #7715 +/- ##
==================================================
- Coverage 3.33% 3.30% -0.04%
==================================================
Files 542 561 +19
Lines 56881 58355 +1474
Branches 839 873 +34
==================================================
+ Hits 1899 1928 +29
- Misses 54982 56427 +1445
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Conflicts: - `.changeset/add-wardley-maps.md` (deleted, due to already being released in v11.14.0)
e10f334 to
1bc37bd
Compare
@mermaid-js/examples
mermaid
@mermaid-js/layout-elk
@mermaid-js/layout-tidy-tree
@mermaid-js/mermaid-zenuml
@mermaid-js/parser
@mermaid-js/tiny
commit: |
ashishjain0512
left a comment
There was a problem hiding this comment.
@aloisklink Thank you for the clean up 👍
📑 Summary
Note
This PR targets the
release/11.15.0instead ofdevelop.701020c was a bad merge, which didn't correctly cleanup the changeset entries that we released as part of v11.14.0.
📏 Design Decisions
N/A
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSIONis used for all new features.pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.