evidence-dev
Add Heatmap to legacy
Checklist
- [ ] For UI or styling changes, I have added a screenshot or gif showing before & after
- [ ] I have added a changeset
⚠️ No Changeset found
Latest commit: c6d3f2211610343494237acbab7a7e0b00a23cc5
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
![changeset-bot[bot] avatar](https://avatars.githubusercontent.com/in/28616?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy Preview for evidence-development-workspace failed.
| Name | Link |
|---|---|
| Latest commit | c6d3f2211610343494237acbab7a7e0b00a23cc5 |
| Latest deploy log | https://app.netlify.com/sites/evidence-development-workspace/deploys/65cc4fa92df37e000892cdac |
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Feb 14, 2024 5:29am |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Should this be pointing to legacy branch instead of next?
Based on line change count this also may have been branched off of next rather than legacy, so we'll need to cherrypick and/or move the changes over to a branch based on legacy if that's the case
@ItsMeBrianD presumably this needs a changeset too? Or do we want to manually version legacy changes?
Dev workspace is going to fail because USQL adds build:sources step which does not exist in legacy
Or do we want to manually version legacy changes?
We can try changesets but we might want to fall back to manual versioning to ensure we don't conflict
can we close this? @hughess - I think we do not need to release this on legacy?