Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[February 2024] eRegs parsing requirements #830

Closed
2 of 4 tasks
pkfec opened this issue Feb 1, 2024 · 0 comments · Fixed by #838
Closed
2 of 4 tasks

[February 2024] eRegs parsing requirements #830

pkfec opened this issue Feb 1, 2024 · 0 comments · Fixed by #838

Comments

@pkfec
Copy link
Contributor

pkfec commented Feb 1, 2024

Take a look at Snyk vulnerabilities for requirements-parsing.txt and upgrade relevant packages to maintain the parsing tool

Reference ticket: #825

Action Items :

  • Check and document parsing requirements and upgrades in Snyk
    • Run: snyk test --file=requirements-parsing.txt --package-manager=pip

Completion criteria:

@pkfec pkfec added this to the Sprint 24.2 milestone Feb 1, 2024
@patphongs patphongs moved this to Assigned in Website project Feb 23, 2024
@cnlucas cnlucas modified the milestones: Sprint 24.2, Sprint 24.3 Feb 27, 2024
@pkfec pkfec moved this from 📥 Assigned to 🏗 In Progress in Website project Feb 28, 2024
@pkfec pkfec moved this from 🏗 In Progress to 👀 Ready in Website project Feb 28, 2024
@github-project-automation github-project-automation bot moved this from 👀 Ready to ✅ Done in Website project Mar 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants