Conversation
…appy path working
Bumps [node-xlsx](https://github.com/mgcrea/node-xlsx) from 0.23.0 to 0.24.0. - [Release notes](https://github.com/mgcrea/node-xlsx/releases) - [Changelog](https://github.com/mgcrea/node-xlsx/blob/master/.release-it.json) - [Commits](mgcrea/node-xlsx@v0.23.0...v0.24.0) --- updated-dependencies: - dependency-name: node-xlsx dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…velop/node-xlsx-0.24.0 build(deps): bump node-xlsx from 0.23.0 to 0.24.0
feat: general logic clarifications
# Conflicts: # src/models/organizations/organizations.model.js
fix: removed rpc call exceeding max response feat: improved logging
feat: rework of tasks to reconcile a organizations stores agains the stores determined by datalayer feat: updated task to update the data model store and hash
…s-v2 V2 fix organization imports v2
feat: checks for PENDING orguid's in relevant functions
fix: bugs
feat: reworked delete organization workflows and endpoints feat: consolidated import and delete resources for home and non-home orgs
Update Managed Files
Release Candidate workflow
Add datamodel to org table
ci: fix mac pkg release names
ci: fix mac pkg release names
ci: fix mac pkg release names
ci: fix mac pkg release names
ci: fix mac pkg release names
ci: switch from j2cli to jinjanate
chore: dep-updates
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
|
@SocketSecurity ignore npm/node-xlsx@0.24.0 |
No description provided.