Add post for release v0.19#209
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new Shipwright blog post announcing the v0.19.0 release, summarizing key Build/CLI updates and providing installation instructions for users of the website documentation.
Changes:
- Introduce a new release announcement post for Shipwright v0.19.0
- Document Build feature highlights (step resources, RuntimeClass, PipelineRun execution mode) and dependency updates
- Provide updated install commands and CLI example snippets for v0.19.0
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
@qu1queee |
There was a problem hiding this comment.
Pull request overview
Adds the Shipwright v0.19.0 release announcement post to the website blog, summarizing notable Build/CLI updates and providing installation instructions.
Changes:
- Introduces a new blog post for the v0.19.0 release announcement.
- Highlights Build feature additions/behavior changes and infrastructure/dependency updates.
- Documents CLI updates and provides install commands for Build and CLI artifacts.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| {{< alert color="info" title="Security Notice: Trivy Compromise (March 2026)" >}} | ||
|
|
||
| On March 19, 2026, the open source Trivy project disclosed a compromise that led to a malicious release of their security scanner (v0.69.4). Shipwright imports the Trivy scanner through the build's image-processing container, which launches security scans when the vulnerability scan feature is enabled in a build. Based on our analysis, Shipwright was not affected by this compromise. None of our nightly releases included the vulnerable version of Trivy, and our current official v0.19.z releases predate the compromise. Current Shipwright adopters and end users are not affected and no further action is required. | ||
|
|
There was a problem hiding this comment.
The security notice references an event on "March 19, 2026", but this post’s front matter date/lastmod is "2026-03-13" (and the filename is 2026-03-13). That makes the post appear to describe an incident that hadn’t happened yet at the time of publication. Please either update the post date/lastmod to reflect when the notice was added, or adjust the notice timeline so it matches the post’s publication date.
|
|
||
| ### RuntimeClass Flag | ||
|
|
||
| The `shp buildrun create` and `shp build run create` command now supports a `--runtime-class` flag, allowing you to specify |
There was a problem hiding this comment.
shp build run create doesn’t match the CLI syntax used elsewhere in the docs (e.g., content/docs/build/runtime-class.md uses shp build run <build> ...). Also, the sentence refers to two commands but uses singular agreement (“command … supports”). Please correct the command name(s) and update the wording (e.g., “commands … support”).
| The `shp buildrun create` and `shp build run create` command now supports a `--runtime-class` flag, allowing you to specify | |
| The `shp buildrun create` and `shp build run <build>` commands now support a `--runtime-class` flag, allowing you to specify |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SaschaSchwarze0 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
Co-authored-by: Sascha Schwarze <schwarzs@de.ibm.com> Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
9080989 to
b974b03
Compare
|
/lgtm |
Changes
Add post entry for v0.19 Release
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes