Extends the build workflow to include the 'epub' format for both development and production environments.
Ensures final status report is always generated.
Removes the workflow_dispatch trigger from the Quarto Build workflow.
This change ensures that the workflow is only triggered by workflow_call, enforcing that it can only be initiated by other workflows and not manually.
Improves the caching mechanism for R packages by including changes in Quarto documents (`.qmd`) in the cache key.
Refactors the artifact uploading logic to upload the entire `_book` directory, providing more flexibility in handling different output formats.
The artifact is only uploaded if the action is triggered by a pull request, the deploy input is false, or the output format is not HTML.
Updates the deployment process to the dev site. It now includes explicit git commands for cloning, cleaning, copying, committing, and pushing changes to ensure proper synchronization. This change restricts the deployment to HTML format only.
This provides more control and robustness during deployment while optimizing the build process.
Changes the condition for installing TeX Live to install if the format is not 'none'.
This ensures that TeX Live is installed for all formats except 'none'.
Adds `dvisvgm` and `pdf2svg` to the list of Linux dependencies
required for the Quarto build process. This ensures these tools
are available during the build, potentially enabling new features or
fixing issues related to SVG processing.
Refines the dev site deployment process by adding validation steps to ensure the content is valid before pushing.
Also, it ensures the deployment is triggered only for HTML format and improves the cloning process by using depth=1 to speed up cloning, adds cleaning steps for existing docs, and includes logic to remove the CNAME file if it exists.
Replaces the `cpina/github-action-push-to-another-repository` action with a shell script for deploying to the dev site.
This provides more control over the deployment process, allowing for easier customization and debugging.
The script clones the target repository, checks out the main branch, copies the generated documentation, commits the changes, and pushes them to the remote repository.
Also configures git user name and email.
Disables verbose debug logging in the Quarto build workflow.
This change reduces the verbosity of the build output
by commenting out the `QUARTO_LOG_LEVEL` environment variable.
Ensures Chromium is installed using either `chromium-browser` or `chromium` package names.
Sets the `CHROMIUM_PATH` environment variable to the correct Chromium executable path, improving reliability on Linux.
Adds a step to install Chromium browser on Linux runners
in the Quarto build workflow. This ensures that Chromium
is available for tasks that rely on it, such as PDF generation.
Also includes a check for Chromium's binary location after
installation to assist with debugging if needed.
Removes the `update-changelog` workflow and its dependencies from the controller workflow.
This change simplifies the workflow and removes an automated changelog update process.
The removal also updates the dependent workflows `build-dev` and `build-main` and the summary jobs.
Removes the `QUARTO_LOG_LEVEL` and `QUARTO_CHROMIUM_HEADLESS_MODE` environment variables.
These were likely added for debugging purposes and are no longer needed.
Sets the `QUARTO_LOG_LEVEL` environment variable to `DEBUG`.
This change facilitates more detailed logging output during Quarto build processes, aiding in troubleshooting and debugging.
Comments out the QUARTO_LOG_LEVEL environment variable in the
Quarto build workflow. The debug logging level is not required
for normal operation and can be enabled when needed.
Sets the `QUARTO_LOG_LEVEL` environment variable to `DEBUG` in the Quarto build workflow.
This allows for more detailed logging output during the build process, which can be helpful for troubleshooting and debugging issues.
Updates the texlive version in the GitHub Actions workflow to the 2025 release.
This ensures the build process uses the latest available TeX distribution, potentially including newer packages, features, and bug fixes.
Comments out the debug log level setting for the Quarto build workflow.
This helps prevent verbose logging output during normal operation,
while retaining the option to easily re-enable it for debugging purposes
by uncommenting the line.
Sets the Chromium headless mode to "new" within the workflow.
This aligns with current best practices for headless environments,
potentially improving stability and compatibility of the build
process.
Sets the `QUARTO_LOG_LEVEL` environment variable to `DEBUG`
in the GitHub Actions workflow.
This provides more detailed logging output during Quarto builds,
which is helpful for debugging purposes.
Improves the readability and clarity of the workflow controller by adding names and emojis to the jobs.
This change also adjusts the status report generation to better reflect the outcome of each workflow step.
Adds the `png` R package and `libpng-dev` Linux dependency to enable handling PNG images in the Quarto build process. This ensures proper rendering and processing of PNG images within the generated output.
The workflow requires `jupyter` to be installed alongside
`jupyterlab-quarto`. This change ensures that both packages
are available during the build process.
Enhances the link checking workflow by excluding mail links, limiting concurrency, accepting specific HTTP status codes, and ignoring broken links to improve accuracy and reduce false positives.
Improves the workflow status report by streamlining the output generation and focusing on key information.
This change also sets `fail-fast: false` to prevent premature workflow termination.
Updates the Python version used in the workflow to 3.13.
Simplifies the installation process by directly installing
jupyterlab-quarto across different operating systems.
Configures Python environment for use in the workflow.
This includes:
- Installing Python 3.12
- Installing required Python packages (jupyter, matplotlib, numpy, pandas)
- Adding Python scripts to PATH on Windows
Relates to jeff/issue-776
Removes the Python setup and package installation steps from the Quarto build workflow. This is likely due to a change in dependencies or a different approach to managing the Python environment.
Ensures Python packages required for the Quarto build are installed correctly on both Windows and Linux runners.
Separates installation steps based on the operating system and uses `pwsh` shell and `py` launcher on Windows.
Adds steps to add Python scripts directory to PATH on Windows runners, ensuring Jupyter can be found and executed.
Verifies the installation by running `jupyter --version` and `python -m jupyter --version`.
Adds a step to set up Python 3.12 and install necessary Python packages (jupyter, matplotlib, numpy, pandas) for the Quarto build process. This ensures the availability of these packages during the Quarto rendering stage, avoiding potential build failures due to missing dependencies.
Adds pull request triggers to the controller workflow.
This allows the workflow to run automatically when pull requests
are created or updated on the main and dev branches, providing
continuous integration for pull requests.
Removes the separate validation build workflow that was triggered on pull requests. This functionality is now incorporated into the standard build jobs, simplifying the workflow configuration.
The "build-dev-light" job is no longer needed,
so this commit removes checks and references to it
in the controller workflow, simplifying the logic
for development build status reporting.
Removes the dedicated lightweight HTML-only build workflow for the `dev` branch.
This simplifies the CI/CD configuration by consolidating build processes. The standard `build-dev` job now handles all `dev` branch builds, ensuring consistency and reducing workflow complexity.
Removes the pull request trigger from the controller workflow.
This change streamlines the workflow execution and avoids
unnecessary runs on pull requests.
Substitutes the deploy action with a shell script,
leveraging git commands directly for enhanced control
and customization during deployment. This change aims
to provide a more flexible and reliable deployment process.
Extends the matrix build to include both Ubuntu and Windows,
ensuring builds for all supported OS formats.
Conditional deployment restricts to only ubuntu.
Fixes issue where only one format was built.
