build: 🔖 Bump version to 1.0.2

[Anselmoo]

All PR-Submissions:

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open
  Pull Requests for the same
  update/change?

New ✨✨ Feature-Submissions:

---

• Does your submission pass tests?
• Have you lint your code locally prior to submission? Fixed:
• This PR is for a new feature, not a bug fix.

Changes to ⚙️ Core-Features:

---

• Have you added an explanation of what your changes do and why you'd like
  us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

Summary by Sourcery

Bumped project version to 1.0.2 and updated the Docker build-push-action in the GitHub Actions workflow.

• Build:
  • Updated Docker build-push-action to a new commit hash in the GitHub Actions workflow.

[semanticdiff-com]

Review changes with SemanticDiff.

Analyzed 3 of 6 files.

	Filename	Status
❔	poetry.lock	Unsupported file format
❔	pyproject.toml	Unsupported file format
✔️	vendor/docker-stacks	Analyzed
✔️	vendor/lmfit-py	Analyzed
✔️	spectrafit/__init__.py	Analyzed
❔	.github/workflows/docker-cd.yml	Unsupported file format

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Docker build-push-action to a newer version and increments the project version from 1.0.1 to 1.0.2. The changes are straightforward and involve modifying the version strings in the respective files.

File-Level Changes

Files	Changes
.github/workflows/docker-cd.yml spectrafit/__init__.py	Updated the Docker build-push-action version and bumped the project version to 1.0.2.

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[phylum-io]

Phylum OSS Supply Chain Risk Analysis - FAILED

This repository analyzes the risk of new dependencies. An
administrator of this repository has set requirements via Phylum policy.

If you see this comment, one or more dependencies have failed Phylum's risk analysis.

Package: [email protected] failed.

[email protected] contains suspicious behavior in the setup.py.

Risk Domain: Malicious Code
Risk Level: low

Reason: Install Code Execution (Suspicious)

Package: [email protected] failed.

[email protected] contains suspicious behavior in the setup.py.

Risk Domain: Malicious Code
Risk Level: low

Reason: Install Code Execution (Suspicious)

Package: [email protected] failed.

[email protected] contains suspicious behavior in the setup.py.

Risk Domain: Malicious Code
Risk Level: low

Reason: Install Code Execution (Suspicious)

Package: [email protected] failed.

[email protected] contains suspicious behavior in the setup.py.

Risk Domain: Malicious Code
Risk Level: medium

Reason: Install Code Execution (Suspicious)

Package: [email protected] failed.

[email protected] contains suspicious behavior in the setup.py.

Risk Domain: Malicious Code
Risk Level: low

Reason: Install Code Execution (Suspicious)

View this project in the Phylum UI

[sourcery-ai]

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

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 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 to tell me if it was helpful.}

[sourcery-ai]

suggestion: Consider using a version tag instead of a commit hash for the docker/build-push-action.

Using a version tag (e.g., @v4) instead of a specific commit hash can make it easier to manage and update the action in the future. It also ensures you're using a stable, tagged release.

Suggested change

	uses: docker/build-push-action@5176d81f87c23d6fc96624dfdbcd9f3830bbe445
	uses: docker/build-push-action@v4

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4c821d8) to head (cae49e9).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1432   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           44        44           
  Lines         4467      4467           
=========================================
  Hits          4467      4467           

Flag	Coverage Δ
unittests	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
spectrafit/__init__.py	100.00% <100.00%> (ø)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud