Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Another attempt to fix dependabot failure to resolve "Slicer/jinja2-action" version #299

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

jcfr
Copy link
Member

@jcfr jcfr commented Jan 8, 2025

This is expected to address the following error introduced in 5abe070 ("fix: Use Slicer fork of jinja2-action to fix Poetry 2.0 breaking change", 2025-01-08)

Dependabot could not find a dependency version.
Dependabot could not resolve semantic versions for dependencies : Slicer/jinja2-action

Instead of listing "Slicer/jinja2-action" as dependency to ignore, this pull request reverts changes originally introduced in #298 and instead changes the comment to include multiple strings and not only one version specifier.

For reference, see https://github.com/dependabot/dependabot-core/blob/e45d543f4556fa040f0b7add3b1184c9b15074fe/github_actions/lib/dependabot/github_actions/file_updater.rb#L88-L94

jcfr added 2 commits January 8, 2025 15:56
…a2-action" version

This is expected to address the following error introduced in 5abe070 ("fix: Use Slicer fork of jinja2-action to fix Poetry 2.0 breaking change", 2025-01-08)

> Dependabot could not find a dependency version.
> Dependabot could not resolve semantic versions for dependencies : Slicer/jinja2-action

Instead of listing "Slicer/jinja2-action" as dependency to ignore, this commit
changes the comment to include multiple strings and not only one version specifier.

For reference, see https://github.com/dependabot/dependabot-core/blob/e45d543f4556fa040f0b7add3b1184c9b15074fe/github_actions/lib/dependabot/github_actions/file_updater.rb#L88-L94
@jcfr jcfr enabled auto-merge (rebase) January 8, 2025 21:08
@slicerbot
Copy link

slicerbot commented Jan 8, 2025

download.slicer.org preview [branch: deploy_download_maintenance_preview]

⚠️ The download preview is a static website generated using mock data 1, is temporary and may be updated at anytime 2

Screenshot from https://deploy-download-maintenance-preview--slicer-org.netlify.app/download.html
Screenshot

Footnotes

  1. See front matter variable download_mock associated with https://raw.githubusercontent.com/Slicer/slicer.org/main/download.markdown

  2. Due to limitation of Netlify preventing us from having multiple deploy previews associated with a single pull request and the impossibility of using repository secret in a workflow associated with a pull-request originating from forks, the deploy-download-preview site is only updated for pull request originating from this repository and will be overriden after another pull request is pushed or updated.

@jcfr jcfr merged commit f2450cf into main Jan 8, 2025
10 checks passed
@jcfr jcfr deleted the fix-dependabot-update-attempt-2 branch January 8, 2025 21:09
@slicerbot
Copy link

slicerbot commented Jan 8, 2025

download.slicer.org preview [branch: deploy_download_preview]

⚠️ The download preview is a static website generated using mock data 1, is temporary and may be updated at anytime 2

Screenshot from https://deploy-download-preview--slicer-org.netlify.app/download_release_and_nightly.html Screenshot from https://deploy-download-preview--slicer-org.netlify.app/download_only_release.html Screenshot from https://deploy-download-preview--slicer-org.netlify.app/download_only_nightly.html
Screenshot Screenshot Screenshot
Screenshot from https://deploy-download-preview--slicer-org.netlify.app/download_release_and_nightly.html
Screenshot

Footnotes

  1. See front matter variable download_mock associated with https://raw.githubusercontent.com/Slicer/slicer.org/main/download.markdown

  2. Due to limitation of Netlify preventing us from having multiple deploy previews associated with a single pull request and the impossibility of using repository secret in a workflow associated with a pull-request originating from forks, the deploy-download-preview site is only updated for pull request originating from this repository and will be overriden after another pull request is pushed or updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants