Skip to main content

Updating Your Pipeline

Keeping Gruntwork Pipelines updated is straightforward. Regular updates are released to ensure optimal performance and scalability for managing infrastructure changes.

Regular updates are released for the Pipelines CLI, associated GitHub Actions Workflows, and custom GitHub Actions. To apply the latest updates across these components, modify the pipelines.yml file located in the .github/workflows directory of any repository integrated with Gruntwork Pipelines. Update the file to reference the latest version of the Pipelines GitHub Actions Workflow:

jobs:
  GruntworkPipelines:
    uses: gruntwork-io-team/pipelines-workflows/.github/workflows/pipelines-root.yml@v3.0.0

Due to our integration with Dependabot, you can automatically receive pull requests suggesting updates to the pipelines.yml file in your repository by including a .github/dependabot.yml file. This ensures your repository stays aligned with the latest changes in Gruntwork Pipelines. DevOps Foundations customers receive this configuration as part of their infrastructure-live repositories by default.

note

Gruntwork recommends leaving your workflow reference at a major-tag shorthand, such as v3 to automatically get the latest minor-tag updates.

Updating customized workflows​

If you have customized workflows as outlined in Extending Pipelines, maintaining updates to these workflows may require additional effort. For those who have forked the pipelines-workflows repository to implement customizations, manual updates will be necessary to incorporate the latest changes from the upstream repository.

To update your workflows, follow the instructions provided in the GitHub documentation. This process applies as long as there are no conflicts between your customizations and the upstream repository.