search

qiskit-community / qiskit-algorithms

A library of quantum algorithms for Qiskit.
https://qiskit-community.github.io/qiskit-algorithms/
Apache License 2.0
89 stars 43 forks source link

Update actions using deprecated Node.js (backport #139) #140

Closed mergify[bot] closed 5 months ago

mergify[bot] commented 5 months ago

This is an automatic backport of pull request #139 done by Mergify. Cherry-pick of b6894e90e45dcd1ff117e50c879a64acdbc96bdc has failed:

On branch mergify/bp/stable/0.2/pr-139
Your branch is up to date with 'origin/stable/0.2'.

You are currently cherry-picking commit b6894e9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
    modified:   .github/workflows/deploy-code.yml
    modified:   .github/workflows/deploy-docs.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   .github/actions/install-main-dependencies/action.yml
    both modified:   .github/workflows/main.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Mergify commands and options
More conditions and actions can be found in the [documentation](https://docs.mergify.com/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport ` will backport this PR on `` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com
woodsp-ibm commented 5 months ago

On reflection backporting this may have not been such a great idea, hence I am going to close this, rather than try to sort out the conflicts and remove the 3.12 jobs, where 3.12 is not supported by stable. If it gets to the point where the actions are needed to be updated in the workflows here then a direct PR to stable can be done on the workflows here to that end.