Skip to content

Bump cryptography from 44.0.0 to 44.0.1#3

Merged
jcschaff merged 1 commit into
mainfrom
dependabot/pip/cryptography-44.0.1
Mar 26, 2025
Merged

Bump cryptography from 44.0.0 to 44.0.1#3
jcschaff merged 1 commit into
mainfrom
dependabot/pip/cryptography-44.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 13, 2025

Copy link
Copy Markdown
Contributor

Bumps cryptography from 44.0.0 to 44.0.1.

Changelog

Sourced from cryptography's changelog.

44.0.1 - 2025-02-11


* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.4.1.
* We now build ``armv7l`` ``manylinux`` wheels and publish them to PyPI.
* We now build ``manylinux_2_34`` wheels and publish them to PyPI.

.. _v44-0-0:

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [cryptography](https://github.com/pyca/cryptography) from 44.0.0 to 44.0.1.
- [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst)
- [Commits](pyca/cryptography@44.0.0...44.0.1)

---
updated-dependencies:
- dependency-name: cryptography
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Feb 13, 2025

@jcschaff jcschaff left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approve bumping this package for security

@jcschaff jcschaff merged commit 60d675f into main Mar 26, 2025
@jcschaff jcschaff deleted the dependabot/pip/cryptography-44.0.1 branch March 26, 2025 16:03
jcschaff added a commit that referenced this pull request Jun 4, 2026
#4 (in-flight SimulationRunWorkflow loses biosim_run_id on replay):
SimulationRunWorkflow now falls back to the nested
output.biosimulator_workflow_run.biosim_run.id when the new
output.biosimulations_run_id field is None. Child OmexSimWorkflowOutput
payloads recorded under pre-PR2.5 code lack the new top-level field;
pydantic defaults it to None on replay. The fallback uses the canonical
id from the historical BiosimulatorWorkflowRun so the parent still
records the external run id even mid-deploy.

#3 (Temporal NonDeterministicWorkflowError for in-flight OmexSimWorkflow):
The activity-sequence change inside OmexSimWorkflow (1 monolithic ->
2 split + optional 1 early-write) is structurally incompatible with
histories recorded by the old code. An @activity.defn(name=...) alias
can't fix it -- the *number* of scheduled activities also differs. The
Temporal-correct workflow.patched() pattern is deferred (substantial
churn for a one-time transition); the pragmatic mitigation is a worker
drain before rollout.

Docs:
- docs/workflows-architecture.md gains a "Deploy considerations"
  section explaining the NDE risk, the drain procedure, the deferred
  workflow.patched alternative, and what replay-safety nets the
  PR2.5 code itself provides.
- backend/CLAUDE.md's Deploy section gets a callout pointing to it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant