fix(ci): make Python version dynamic

[Nidhi091999]

Resolves: #67

Summary by Sourcery

CI:

• Use the Python version defined by cookiecutter.python_version in the vulnerability check workflow.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request makes the python version in the vulnerability workflow dynamic by using the cookiecutter variable.

Flow diagram for dynamic Python version in vulnerability workflow

graph TD
    A[Cookiecutter Template] -->|python_version variable| B[vulnerability.yaml]
    B -->|Used in| C[Poetry Setup Action]
    C -->|Configures| D[Python Version for Vulnerability Checks]
    style A fill:#f9f,stroke:#333,stroke-width:2px
    style B fill:#bbf,stroke:#333,stroke-width:2px
    style C fill:#dfd,stroke:#333,stroke-width:2px
    style D fill:#fdd,stroke:#333,stroke-width:2px

Loading

File-Level Changes

Change	Details	Files
Make python version dynamic in vulnerability workflow.	Replaced hardcoded python version with cookiecutter variable in the vulnerability workflow.	{{ cookiecutter.project_name_dashed }}/.github/workflows/vulnerability.yaml

Possibly linked issues

• fix(ci): python verison is hardcoded.  #67: The PR changes Python version to dynamic in vulnerability.yaml, addressing the issue of hardcoded version.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Nidhi091999 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[uniqueg]

Thanks a lot, @Nidhi091999! LGTM, but I would like @JaeAeich to have a look as well before merging.

[JaeAeich]

Please do the same in actions.yaml as well for inputs.python_version.

Note the raw tag, you will have to bring that below otherwise jinja templating wont work.

[JaeAeich]

Please see the comment.

[Nidhi091999]

Please do the same in actions.yaml as well for inputs.python_version.

Note the raw tag, you will have to bring that below otherwise jinja templating wont work.

Done

[JaeAeich]

One way to test if your changes are good and not breaking anything is to:

• Commit you changes (it wont work without committing).
• Run cruft create . and keep pressing enter till it create a project names python-cookiecutter.
• cd python-cookiecutter
• git init; git add .; git commit -m "init"
• make fl, note this should not change anything, check in git diff or vscode git tab, if it does change anything you need to make changes.
• make pc, same as above, shouldn't change anything.

Note: There is a possibility that you some of the hooks when you run make pc break, which might not be your fault, we have issues open for them and will be fixed later, the easiest way to do this is create another project ie cruft create . on main branch and compare.

[JaeAeich]

We will implement CI for all of this stuff maybe you can take the initiative if you want, happy to help. Wasn't a priority for us, but I can see the need now.

@Nidhi091999 maybe open an issue for this with title like ci: implement CI/CD or something.

[Nidhi091999]

One way to test if your changes are good and not breaking anything is to:

• Commit you changes (it wont work without committing).
• Run cruft create . and keep pressing enter till it create a project names python-cookiecutter.
• cd python-cookiecutter
• git init; git add .; git commit -m "init"
• make fl, note this should not change anything, check in git diff or vscode git tab, if it does change anything you need to make changes.
• make pc, same as above, shouldn't change anything.

Note: There is a possibility that you some of the hooks when you run make pc break, which might not be your fault, we have issues open for them and will be fixed later, the easiest way to do this is create another project ie cruft create . on main branch and compare.

Thank you for the commands. I have tested my changes, and there are no liniting issues. However, there are some linting warnings in other parts of the code, which I will address in a separate PR shortly.

[JaeAeich]

LGTM!! Nice :)

[JaeAeich]

@Nidhi091999 seems like your commits aren't verified, maybe go ahead and create a gpg key, add it to github and so that all your other commits are verified.

look into these instruction.

[Nidhi091999]

@Nidhi091999 seems like your commits aren't verified, maybe go ahead and create a gpg key, add it to github and so that all your other commits are verified.

Thanks for the instructions! I've generated a new GPG key and added it to GitHub.

[JaeAeich]

@uniqueg these changes are good, maybe lets bypass the verified signature rule for now, given @Nidhi091999's further changes will be verfied 🚀