You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
flowchart LR
A["New Bruno 2.9.1"] --> B["Configuration File"]
A --> C["Build Properties"]
A --> D["Release Registry"]
B --> E["bruno.exe executable"]
C --> F["Updated release date"]
D --> G["Download URL mapping"]
Verify that the new brunoVersion and brunoExe keys match expected naming and schema across existing versions to avoid loader/parsing issues, and ensure the path/version folder bruno2.9.1 aligns with tooling that discovers configs.
Confirm the 2.9.1 download URL and date stamp resolve correctly and follow the established naming pattern; a mismatch here will break automated downloads.
Drop the surrounding quotes to match typical key=value semantics used by other module configs and avoid accidental inclusion of quotes in parsed values. Ensure values are plain strings unless the parser explicitly requires quoting.
Why: This suggestion correctly points out that removing quotes for simple values in config files is good practice, which enhances robustness by preventing potential parsing issues.
Low
Remove extraneous blank lines
Remove unnecessary blank lines to avoid misparsing by strict properties parsers and to keep formatting consistent with the rest of the file. Properties files typically use comments or contiguous key-value pairs without extra separators.
Why: This is a minor stylistic suggestion that reverts the addition of blank lines, aligning with the file's previous format and potentially improving compatibility with strict parsers.
✅ Validate release URL patternSuggestion Impact:The commit includes the 2.9.1 URL with matching version and date as suggested, effectively implementing the validation by adding the correct entry; it also added 2.9.0 similarly.
URL components must exactly match the tag and artifact naming conventions; ensure the tag path and filename both include the same version and date. If your release tag uses a different pattern (e.g., v2.9.1), adjust the URL accordingly to prevent 404s.
Why: This is a valuable suggestion as it prompts the user to verify the newly added release URL, which is critical for functionality, and an incorrect URL would lead to a broken download link.
Medium
General
Remove unnecessary quotes
Remove the surrounding quotes to keep consistency with typical key=value config parsing, which may treat quoted values literally. This avoids downstream scripts reading the quotes as part of the value.
Why: The suggestion offers a reasonable style improvement by removing quotes, which can enhance consistency and prevent potential parsing issues depending on the configuration file parser.
✅ Align config version with releaseSuggestion Impact:The commit updated brunoVersion from "2.8.1" to "2.9.1" exactly as suggested.
code diff:
-brunoVersion = "2.8.1"+brunoVersion = "2.9.1"
Update the brunoVersion to match the new 2.9.1 release to avoid version mismatch issues. Ensure the config aligns with the corresponding release entry and directory name.
Why: The suggestion correctly identifies a critical version mismatch where the new config file bin/bruno2.9.1/bearsampp.conf has brunoVersion set to "2.8.1" instead of "2.9.1", which could cause runtime errors.
High
General
✅ Ensure release URL consistencySuggestion Impact:The committed change adds version 2.9.0 with a URL matching the established naming pattern and keeps versions in sorted order, aligning with the suggestion’s intent to ensure consistency and sorting.
Verify the new URL follows the exact naming convention used by previous releases, including date and artifact pattern. If tooling parses in order, keep entries sorted by version to prevent unexpected selection behavior.
Why: The suggestion asks to verify URL naming conventions and version sorting, which are good practices, but the code in the PR already follows these conventions correctly, making the suggestion a minor verification prompt.
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.
![qodo-merge-pro[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
PR Type
Enhancement
Description
Add Bruno 2.9.1 version configuration
Update bundle release date to 2025.8.15
Add new release entry for version 2.9.1
Diagram Walkthrough
File Walkthrough
bearsampp.conf
Add Bruno 2.9.1 configuration filebin/bruno2.9.1/bearsampp.conf
build.properties
Update bundle release datebuild.properties
releases.properties
Register Bruno 2.9.1 releasereleases.properties