2 Commits

Author SHA1 Message Date
HarithaVattikuti
5d0a8ceaea Audit fix 2025-01-16 08:43:27 -06:00
HarithaVattikuti
0a555c8d11 Add permissions section 2025-01-16 08:27:22 -06:00
2 changed files with 9 additions and 22 deletions

View File

@@ -1,22 +0,0 @@
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
version: 2
updates:
# Enable version updates for npm
- package-ecosystem: 'npm'
# Look for `package.json` and `lock` files in the `root` directory
directory: '/'
# Check the npm registry for updates every day (weekdays)
schedule:
interval: 'weekly'
# Enable version updates for GitHub Actions
- package-ecosystem: 'github-actions'
# Workflow files stored in the default location of `.github/workflows`
# You don't need to specify `/.github/workflows` for `directory`. You can use `directory: "/"`.
directory: '/'
schedule:
interval: 'weekly'

View File

@@ -20,6 +20,15 @@ Read more about action versioning notation in [action-versioning.md](https://git
To roll back a release in case of customer impact, start the workflow manually and specify the previous stable tag.
## Recommended permissions
When using the `publish-action` in your GitHub Actions workflow, it is recommended to set the following permissions to ensure proper functionality:
```yaml
permissions:
contents: write # access to publish release
```
## Conributions
We don't accept contributions until the action is ready for production.