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

Fix update cis #3587

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

mmahmoudian
Copy link
Member

I've updated everything to the latest minor or major version depending on if they have their major version tag following their latest stable minor version tag or not.

I have kept the actions/upload-artifact back in v3 because:

  1. It seems there are breaking changes between v3 -> v4 (more info)
  2. there is a PR (Update Windows-pack.yml: update dependencies #3586) that have tried to update this for the Windows CI, so I would not change it to avoid duplicate and confusion

@@ -555,7 +563,7 @@ jobs:
echo "================================"
echo "VERSION=${last_committed_tag:1}" >> $GITHUB_ENV
- name: Packaging snap
uses: snapcore/action-build@v1
uses: snapcore/action-build@v1.2.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
uses: snapcore/action-build@v1.2.0
uses: snapcore/action-build@v1

v1 will install latest v1 version ;)

@@ -84,7 +90,7 @@ jobs:
echo "VERSION=$(cat CMakeLists.txt |grep 'set.*(.*FLAMESHOT_VERSION' | sed 's/[^0-9.]*//' |sed 's/)//g')" >> $GITHUB_ENV

- name: Restore from cache and run vcpkg
uses: lukka/run-vcpkg@v11
uses: lukka/run-vcpkg@v11.5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
uses: lukka/run-vcpkg@v11.5
uses: lukka/run-vcpkg@v11

with:
path: ./build/Qt/${{ matrix.qt_ver }}/${{ matrix.config.qt_arch_install }}
key: ${{ runner.os }}-QtCache/${{ matrix.qt_ver }}/${{ matrix.config.qt_arch }}

- name: Install Qt
uses: jurplel/install-qt-action@v2
uses: jurplel/install-qt-action@v3.3.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
uses: jurplel/install-qt-action@v3.3.0
uses: jurplel/install-qt-action@v3

with:
path: ./build/Qt
key: ${{ runner.os }}-QtCache

- name: Install Qt
uses: jurplel/install-qt-action@v2
uses: jurplel/install-qt-action@v3.3.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
uses: jurplel/install-qt-action@v3.3.0
uses: jurplel/install-qt-action@v3

@mmahmoudian
Copy link
Member Author

@Saibamen It is not clear in the Github documentation if there is a difference between @v4 and @v4.3.2. Bascially if @v4 means 4.0.0 tag or 4 tag, or latest of 4.x.x tags.

In some workflows, they move their major version tag to the latest minor version (e.g v1 always updated to the latest of v1.x.x: https://github.com/snapcore/action-build/tags ), but this does not happen in all workflows (e.g. https://github.com/jurplel/install-qt-action/tags )

Do you know how for example the @v4 is handled by Github Actions?

@mmahmoudian mmahmoudian requested a review from Saibamen May 3, 2024 12:36
@Saibamen
Copy link
Contributor

Saibamen commented May 7, 2024

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

Successfully merging this pull request may close these issues.

None yet

2 participants