Since craft-actions are being used by a couple of different craft projects, with, i'm sure, more to come; we should add version tags and use these, instead of @main (see, for example, here. See, for example, the tagging pattern from https://github.com/canonical/rocks-template-actions/:
$ git log --oneline --decorate=short (git rev-parse HEAD)
07e34ea (HEAD -> main, origin/main, origin/HEAD) chore(deps): update actions/checkout action to v5 (#6)
8481c57 chore(deps): update actions/upload-artifact action to v5 (#10)
6e668ae (tag: v1.1.1, tag: v1.1, tag: v1) bugfix(ci): chdir to repo root when parsing ci.yaml (#8)
ee21b7a (tag: v1.1.0) feat: add support for user-defined registries (#7)
aa5f8bb ci: add test workflow (#5)
b2aed0e chore(deps): update actions/setup-python action to v6 (#3)
a8f1615 (tag: v1.0.0) chore: Configure Renovate
a87f567 doc: update readme
ce895bd feat: add ci yaml reader
96e0e3a chore: move actions to root
bf162fa feat: use github.action_path
873bd2b Revert "chore: move action to root"
48ba0d7 Revert "chore: change paths"
c4dba23 chore: change paths
501017f chore: move action to root
0b30fef feat: allow input path
bc250b0 feat: add read-ci-config
4fb1d52 feat: initial commit
Since craft-actions are being used by a couple of different craft projects, with, i'm sure, more to come; we should add version tags and use these, instead of
@main(see, for example, here. See, for example, the tagging pattern from https://github.com/canonical/rocks-template-actions/: