Release 2.4.0 - #360
Merged
Merged
Release 2.4.0#360
Conversation
Bump version.py, setup.py and the CLI version fixture to 2.4.0, regenerate example/robot_dashboard.html and example/robot_results.db from the current source, and add the 2.4.0 CHANGELOG section. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Changelog entry for #362 and example dashboard/database regenerated so the committed example carries the upward-opening filter dropdowns. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… docs deploy deploy.yml no longer runs on tag pushes, so the docs build started by the release merge usually runs before the tag exists. Document the order: tag the merge commit, create the GitHub Release, then re-run the deploy with workflow_dispatch. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Release actions for 2.4.0 (
releaseskill).Changes
robotframework_dashboard/version.pyRobotdashboard 2.4.0setup.pyversion="2.4.0"tests/robot/resources/cli_output/version.txt--versionCLI testexample/robot_dashboard.html,example/robot_results.dbpython scripts/example.py(18 fixture runs, tags, versions, timezones, custom filters, message config)CHANGELOG.mdThe regenerated example carries the changes that were deliberately left out of their own PRs: the date histogram, the per-project amount filter default view, the section tracks and the modal/popup CSS fixes.
Scope
Nine PRs since v2.3.0: #346 (filter option counts and greying out), #349 (custom filter attributes on the Overview run cards), #350 (amount and retention limit per project, Overview filter reset), #351 (segmented section tracks and collapsible sidebar groups), #352 (docs deploy trigger), #355 (source file splits, modal scroll lock, popup placement), #357 (drag to select date histogram), #359 (dev docs example rebuild), #362 (filter dropdowns open upwards when there is no room below).
Full diff: v2.3.0...release/2.4.0
After merge
Tag
v2.4.0onmain, then verify the docs deploy:/shows v2.4.0 in the nav bar,/v2.4.0/exists, andversions.jsonlists it with"latest": true.Slack release notes are prepared separately.
🤖 Generated with Claude Code