[Snyk] Security upgrade python from 3.12.3-alpine to 3.13.0rc1-alpine

[anselmbradford]

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• Dockerfile.mac_chip

We recommend upgrading to python:3.13.0rc1-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Integer Overflow or Wraparound SNYK-ALPINE320-EXPAT-7908298	786
	Integer Overflow or Wraparound SNYK-ALPINE320-EXPAT-7908299	786
	XML External Entity (XXE) Injection SNYK-ALPINE320-EXPAT-7908300	786
	Use After Free SNYK-ALPINE320-BUSYBOX-7233533	514
	Use After Free SNYK-ALPINE320-BUSYBOX-7233586	514

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 XML External Entity (XXE) Injection
🦉 Use After Free

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.

[jcadam14]

See #205

[jcadam14]

@anselmbradford Not sure why this was reopened. We won't be moving to python 3.13 until its official release on Oct 1, and after making sure everything works right (which I can't imagine a minor release wouldn't be still will be testing our baselines with it). And Orc2 is the current release candidate, not Orc1 as this PR requests. So this PR should be rejected as it references a non-official baseline of python to move to and that's something we're just not going to do.

[anselmbradford]

@jcadam14 I have no idea why this is coming from my account, it's an automated Snyk message that is somehow masquerading as me. I'll do some investigating…

[jcadam14]

Got rid of Dockerfile.mac_chip to remove snyk errors

[lchen-2101]

think we can just close this (and other) snyk PRs that relate to the mac chip dockerfile? since the dockerfile removal resolved the issue, and there are no changes

[jcadam14]

think we can just close this (and other) snyk PRs that relate to the mac chip dockerfile? since the dockerfile removal resolved the issue, and there are no changes

When I previously tried closing it,