Version 2.5.1 and changelog

[i-oden]

Read this before submitting the PR

1. Always create a Draft PR first
2. Go through sections 1-5 below, fill them in and check all the boxes
3. Make sure that the branch is updated; if there's an "Update branch" button at the bottom of the PR, rebase or update branch.
4. When all boxes are checked, information is filled in, and the branch is updated: mark as Ready For Review and tag reviewers (top right)
5. Once there is a submitted review, implement the suggestions (if reasonable, otherwise discuss) and request an new review.

If there is a field which you are unsure about, enter the edit mode of this description or go to the PR template; There are invisible comments providing descriptions which may be of help.

1. Description / Summary

Change version to 2.5.1 and update changelog.

2. Jira task / GitHub issue

DDS-1635

3. Type of change

What type of change(s) does the PR contain?

Check the relevant boxes below. For an explanation of the different sections, enter edit mode of this PR description template.

• New feature
  • Breaking: Why / How? Add info here.
  • Non-breaking
• Bug fix
• Security Alert fix
• Documentation
• Workflow
• Tests only

4. Additional information

• Sprintlog
• Blocking PRs
  • Merged
• PR to master branch: _If checked, read the release instructions
  • I have followed steps 1-8.

5. Actions / Scans

• Black: Python code formatter. Does not execute. Only tests.
  Run black . locally to execute formatting.
  • Passed
• Pylint: Python code linter. Does not execute. Only tests.
  Fix code producing warnings. Code must get 10/10.
  • Warnings fixed
  • Passed
• Prettier: General code formatter. Our use case: MD and yaml mainly.
  Run npx prettier --write . locally to execute formatting.
  • Passed
• Yamllint: Linting of yaml files.
  • Passed
• Tests: Pytest to verify that functionality works as expected.
  • New tests added
  • No new tests
  • Passed
• TestPyPi: Build CLI and publish to TestPyPi in order to verify before release.
  • Passed
• CodeQL: Scan for security vulnerabilities, bugs, errors
  • New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
  • Alerts fixed: What?
  • Alerts ignored / dismissed: Why?
  • Passed
• Trivy: Security scanner
  • New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
  • Alerts fixed: What?
  • Alerts ignored / dismissed: Why?
  • Passed
• Snyk: Security scanner
  • New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
  • Alerts fixed: What?
  • Alerts ignored / dismissed: Why?
  • Passed

[codecov]

Codecov Report

Merging #654 (3cd9551) into dev (0daaff2) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev     #654   +/-   ##
=======================================
  Coverage   46.74%   46.74%           
=======================================
  Files          31       31           
  Lines        2792     2792           
=======================================
  Hits         1305     1305           
  Misses       1487     1487           

Files Changed	Coverage Δ
dds_cli/version.py	100.00% <100.00%> (ø)

[rv0lt]

Should this be marked ?

[i-oden]

Should this be marked ?

No only in the PRs from dev to master

[rv0lt]

Should this be marked ?

No only in the PRs from dev to master

Ah, yes. I got confussed with the other PR 🤦

[i-oden]

Should this be marked ?

No only in the PRs from dev to master

Ah, yes. I got confussed with the other PR 🤦

Understandable!

[rv0lt]

I dont' see anything weird