chore: Bump version to 0.4.0-beta.2 - #98
Merged
Merged
Conversation
Second beta of the Albacore release, cut from the work merged on main since the first beta: git-source deployment, the update-management view, host charts with agent scheduling, and alerts that pick their targets, name the responsible containers, and can restart the offending deployment. Albacore is still unfinished; the open items continue after this beta.
Code Review SummaryThis PR bumps the version to 🚀 Key Improvements
💡 Minor Suggestions
|
![sourceant[bot]](https://avatars.githubusercontent.com/in/1161781?s=60&v=4){kind=small}
Comment on lines
+8
to
+12
| - From Git option in the new-deployment flow: clone a repository and deploy its compose file, with a private repository authenticated by a saved credential or a token that can be saved for reuse | ||
| - Administration > Updates: the current version and the releases available on a channel (stable, or prereleases behind an opt-in), each with its changelog, installing the newest in one click behind the settings permission | ||
| - Host charts on the observability screen for host CPU, memory and disk, with an alert rule able to target a host metric; the host section is hidden when its endpoint is absent instead of breaking the view | ||
| - Agent scheduling from a cadence picker with a permissions selector instead of hand-typed frontmatter, and a per-agent list of past runs that open in the assistant | ||
| - Deleting a saved assistant conversation, behind a confirmation |
There was a problem hiding this comment.
Adding PR references to each entry improves traceability. It allows developers and users to easily locate the original discussion, implementation details, and linked issues in the repository.
Suggested change
| - From Git option in the new-deployment flow: clone a repository and deploy its compose file, with a private repository authenticated by a saved credential or a token that can be saved for reuse | |
| - Administration > Updates: the current version and the releases available on a channel (stable, or prereleases behind an opt-in), each with its changelog, installing the newest in one click behind the settings permission | |
| - Host charts on the observability screen for host CPU, memory and disk, with an alert rule able to target a host metric; the host section is hidden when its endpoint is absent instead of breaking the view | |
| - Agent scheduling from a cadence picker with a permissions selector instead of hand-typed frontmatter, and a per-agent list of past runs that open in the assistant | |
| - Deleting a saved assistant conversation, behind a confirmation | |
| +- From Git option in the new-deployment flow: clone a repository and deploy its compose file, with a private repository authenticated by a saved credential or a token that can be saved for reuse (#95) | |
| +- Administration > Updates: the current version and the releases available on a channel (stable, or prereleases behind an opt-in), each with its changelog, installing the newest in one click (#94) | |
| +- Host charts on the observability screen for host CPU, memory and disk, with an alert rule able to target a host metric (#96) | |
| +- Agent scheduling from a cadence picker with a permissions selector, and a per-agent list of past runs that open in the assistant (#96) | |
| +- Deleting a saved assistant conversation, behind a confirmation (#96) |
|
|
||
| ### Fixed | ||
| - A notification target no longer disappears after a successful test and save; the filled-in draft is pulled into the list on save | ||
| - The Agents, API keys and users views referenced design tokens that do not exist, so borders and surfaces dropped out (the Agents editor input had no visible border in dark mode); all three now use the design system's real tokens |
There was a problem hiding this comment.
This entry is quite verbose for a changelog. A more concise description focusing on the fix and its impact makes the log easier to scan.
Suggested change
| - The Agents, API keys and users views referenced design tokens that do not exist, so borders and surfaces dropped out (the Agents editor input had no visible border in dark mode); all three now use the design system's real tokens | |
| +- Fixed missing borders and surfaces in Agents, API keys, and Users views caused by non-existent design token references (#92) |
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.
Second beta of the Albacore release (flatrun/agent#158), cut from the work merged on main since the first beta. Albacore is unfinished; the open items continue after this beta.