If you believe you have discovered a security vulnerability in Oso, please send details of the issue to [email protected]. Please do not open a GitHub issue or otherwise comment about the issue in a public forum.
If you're struggling to get set up with Oso or have questions about usage, check out the documentation or join us on Slack to ask questions.
If you would like to report a bug, please first ensure that the bug has not already been reported by searching the project's open issues on GitHub.
If you can't find an existing issue, please open a new one. Be sure to include as much detail as possible, including a reproducible code sample.
If you would like to contribute to this project, please open a pull request with your changes. If you haven't already read and signed our Contributor License Agreement, you will be asked to do so upon opening your first PR. Thank you for contributing!
These steps are only relevant to Oso employees when preparing and publishing a new SDK release.
- Create a new branch off of
main. Push the branch to remote. - Run
yarn lerna version --no-private. This pushes versioning commits and release package to remote. - Create a PR towards the
mainbranch. - After the PR is merged, publish the release using the publish workflow.