v0.3.11

github-actions released this 22 May 20:20

· 75 commits to refs/heads/main since this release

5bfb50c

What's Changed

Version.njk: Bump version to 0.3.11 @makubacki (#141)

Change Details

Updates the version for an upcoming release.

MdbookWorkflow.yml: Call the `test-mdbook` task @makubacki (#140)

Change Details

A new task was added to patina called `test-mdbook` that builds and tests the mdbook, encapsulating the logic previously in this workflow. This updates the workflow to reuse that task, so CI and local operations are the same.
The workflow is very simple now but retained as a callable workflow since it still provides a common/reusable place to put any future mdbook related CI logic and reduces some duplication in calling workflows.

The only caller into this reusable workflow today is in the patina repo. The only other Patina-related repo that publishes an mdbook is patina-qemu.

The task can be added to patina-qemu as well when it begins using this workflow.

Note: Not considered "breaking" since the workflow is called from ci-workflow.yml which is synced from this repo and has been updated to remove the parameters no longer in the workflow. A patina-devops version update must also be made in the same file sync so the file references the latest version that calls the cargo-make task.

Tested on fork in this run: https://github.com/makubacki/patina/actions/runs/26247006985/job/77247864402

mdbook Upates [Rebase \& FF] @makubacki (#139)
Change Details
A few updates related to recent mdbook changes.

mdbook: Update dependencies

Updates dependencies to the latest compatible versions. The latest
mdbook release is 0.5.2 but the latest mdbook-admonish release 1.20.0
is not compatible with mdbook 0.5.x. So, mdbook is updated to the
latest 0.4.x release, which is 0.4.52.

Note:

mdbook-admonish might give a warning like the following:
```
Warning: The mdbook-admonish preprocessor was built against version
0.4.51 of mdbook, but we're being called from version 0.4.52
```
That hasn't been observed to be a problem. Nearby versions of
mdbook-mermaid are built against 0.4.52, so they would give a similar
warning if mdbook were downgraded.

Sync updates for adding mdbook to patina-qemu
1. Sync the publish-mdbook.yml workflow to patina-qemu
2. Add an entry to .gitignore in patina-qemu for the mdbook output
  directory

Sync mdbook changes from the patina repository [Rebase \& FF] @makubacki (#137)

Change Details

Syncs additional changes for building and publishing the mdbook from the patina repository.

.sync: Do not attempt to deploy on forks in publish-mdbook.yml

Most forks are likely not intending to publish the Patina mdbook
on their fork repository. Skip the deployment step on forks.

This change is already in place in the patina repository. This is just
syncing it to patina-devops.

.sync: Add mdbook-linkcheck to rust-toolchain.toml

Syncs the mdbook-linkcheck dependency in rust-toolchain.toml to match
what is used in the patina repository.

.sync: Update mdbook from html directory in publish-mdbook.yml @makubacki (#134)

Change Details

Updates the mdbook build artifacts to be uploaded from docs/book/html instead of docs/book because when mdbook has multiple output backends ([output.html] and [output.linkcheck]), it nests output in subdirectories under the build dir (e.g., book/html/, book/linkcheck/) instead of writing directly to book/.

.sync: Use pull\_request\_target for Rust version check workflow @makubacki (#136)

Change Details

This workflow needs to use secrets for PRs from public forks, which is not available with the pull_request trigger currently used.
pull_request_target is used instead since it allows access to secrets and the workflow is limited to simple toml parsing and validation not executing any code from the PR.

Tested on a pull request to a PR from a public fork here: makubacki/patina#13

Full Changelog: v0.3.10...v0.3.11

Contributors

makubacki

Assets 2