Update dependency pyasn1-modules to v0.4.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pyasn1-modules (changelog)	^0.2.8 → ^0.4.0
pyasn1-modules (changelog)	==0.2.8 → ==0.4.2

---

Release Notes

pyasn1/pyasn1-modules (pyasn1-modules)

v0.4.2

Compare Source

• Updated dependency constraint to be compatible with pyasn1 0.6.1, which
  removed the pyasn1.compat.octets module

v0.4.1

Compare Source

• Added support for Python 3.13

v0.4.0

Compare Source

• Added support for Python 3.11, 3.12
• Removed support for EOL Pythons 2.7, 3.6, 3.7

v0.3.0

Compare Source

• Added support for Python 3.8, 3.9, 3.10, 3.11
• Removed support for EOL Pythons 2.4, 2.5, 2.6, 3.2, 3.3, 3.4, 3.5
• Added support for PyPy 3.7, 3.8, 3.9
• Modernized packaging and testing. pyasn1-modules now uses setup.cfg,
  pyproject.toml, build, and
  GitHub Actions.
• PyPI package ownership for pyasn1 and pyasn1-module has been
  transfered to Christian Heimes and Simon Pichugin in
  PyPI support ticket #​2090.
• The upstream repositories for pyasn1 and pyasn1-modules are now
  in the GitHub organization https://github.com/pyasn1/.
• Added tox runner with a handful of basic jobs
• Add RFC3125 providing Electronic Signature Policies
• Add RFC5126 providing CMS Advanced Electronic Signatures (CAdES)
• Removed support for EOL Pythons 2.4, 2.5, 2.6, 3.2, 3.3 and 3.4.
• Improve test routines for RFC5126
• Add RFC4387 providing Certificate Store Access via HTTP
• Changed assertion in unit tests from Python built-in to unittest
  provided
• Add RFC8692 providing Algorithm Identifiers for RSASSA-PSS and
  ECDSA Using SHAKEs
• Add RFC5753 providing CMS Elliptic Curve Cryptography Algorithms
• Add RFC3820 providing Proxy Certificates
• Add RFC3370 providing Cryptographic Message Syntax (CMS) Algorithms
• Add RFC3537 providing HMAC Key Wrapping
• Add RFC3739 providing Qualified Certificates
• Add RFC2876 providing KEA and SKIPJACK for CMS
• Add RFC3058 providing IDEA Encryption Algorithm for CMS
• Add RFC3657 providing Camellia Encryption Algorithm for CMS
• Add RFC4010 providing SEED Encryption Algorithm for CMS
• Add RFC4357 providing Additional Cryptographic Algorithms for Use with
  GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94
• Add RFC4490 providing GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94,
  and GOST R 34.10-2001 Algorithms for CMS
• Add RFC4491 providing GOST R 34.10-94, GOST R 34.10-2001, and
  GOST R 34.11-94 Algorithms for certificates and CRLs
• Add RFC8696 providing using Pre-Shared Key (PSK) in the CMS
• Add RFC5639 providing identifiers for the Brainpool curves in
  Elliptic Curve Cryptography
• Add RFC5697 providing Other Certificates Extension
• Add RFC4683 providing Subject Identification Method (SIM)
• Add RFC4476 providing Attribute Certificate Policies Extension
• Add RFC5636 providing Traceable Anonymous Certificate
• Add RFC5752 providing Multiple Signatures attribute for CMS
• Add RFC5275 providing CMS Symmetric Key Management and Distribution
• Add RFC8702 providing SHAKE One-way Hash Functions in the CMS
• Add RFC8708 providing HSS/LMS Hash-based Signature Algorithm for CMS
• Advance copyright statement to year 2020
• Add RFC8769 providing CBOR and CBOR Sequence content types for CMS

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Creating virtualenv autocsr-EwhKHD6C-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...


The current project's Python requirement (>=3.7,<4.0) is not compatible with some of the required packages Python requirement:
  - pyasn1-modules requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8

Because pyasn1-modules (0.4.0) requires Python >=3.8
 and no versions of pyasn1-modules match >0.4.0,<0.5.0, pyasn1-modules is forbidden.
So, because autocsr depends on pyasn1-modules (^0.4.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pyasn1-modules, a possible solution would be to set the `python` property to ">=3.8,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...


The current project's Python requirement (>=3.7,<4.0) is not compatible with some of the required packages Python requirement:
  - pyasn1-modules requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pyasn1-modules requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pyasn1-modules requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8

Because no versions of pyasn1-modules match >0.4.0,<0.4.1 || >0.4.1,<0.4.2 || >0.4.2,<0.5.0
 and pyasn1-modules (0.4.0) requires Python >=3.8, pyasn1-modules is forbidden.
And because pyasn1-modules (0.4.1) requires Python >=3.8, pyasn1-modules is forbidden.
So, because pyasn1-modules (0.4.2) requires Python >=3.8
 and autocsr depends on pyasn1-modules (^0.4.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pyasn1-modules, a possible solution would be to set the `python` property to ">=3.8,<4.0"
    For pyasn1-modules, a possible solution would be to set the `python` property to ">=3.8,<4.0"
    For pyasn1-modules, a possible solution would be to set the `python` property to ">=3.8,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers