chore(release): update version - #295
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 3, 2026 10:38
156caa2 to
2bf05e9
Compare
timothygachengo
self-requested a review
September 3, 2026 11:49
timothygachengo
approved these changes
Sep 3, 2026
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@devgateway/dvz-ui-react@1.9.13
Patch Changes
#294
d4aab6aThanks @timothygachengo! - preserve Superset filter default values during initialization#293
0155471Thanks @timothygachengo! - Add extra tooltips configuration in d3Maptemplates.
full row data instead of a hardcoded
{name_en}.nested dimension-tree children into flat tooltip variables - the actual
root cause blocking "extra" API columns from ever reaching a tooltip.
extraTooltipColumnsconfig that requests additionalfields via
includeColumns, across DataLayer/LatLongLayer/FlowLayer/Legends, and exclude columns already used as a query dimension (the API
500s if a column is requested both ways).
non-filter param changes (e.g. editing extraTooltipColumns in the block
editor) never triggered a refetch.
mismatched params, letting the legend's fetch silently clobber the map's
correctly-parameterized data.