Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,4 @@
# Markdown and Python normalize to LF for cross-platform consistency.
*.md text eol=lf
*.py text eol=lf
.github/workflows/*.lock.yml linguist-generated=true
9 changes: 9 additions & 0 deletions .github/aw/actions-lock.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"entries": {
"github/gh-aw-actions/setup@v0.87.10": {
"repo": "github/gh-aw-actions/setup",
"version": "v0.87.10",
"sha": "bc8c008a419c5b7a29df6f5641edd35fd1c6ea85"
}
}
}
28 changes: 2 additions & 26 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -1,36 +1,14 @@
version: 2

# NOTE on `target-branch` and security updates
#
# `target-branch: "develop"` below applies ONLY to scheduled *version* updates.
# Dependabot *security* updates (the ones opened in response to a Dependabot
# alert) always target the repository's DEFAULT branch — `main` — and ignore
# `target-branch`. There is no configuration option that changes this.
#
# Because `docs/release-process.md` uses git flow, and `.github/workflows/ci.yml`
# only triggers on `develop`, a security PR left on `main` would both bypass the
# release process and run zero tests (only `license/cla`).
#
# When a security PR appears against `main`, re-cut it against `develop`:
# 1. Create a branch from `develop`.
# 2. Cherry-pick the Dependabot commit (they are lockfile-only, so this is
# usually clean).
# 3. Open a PR to `develop` and close the original with a pointer to it.
# Do NOT simply `gh pr edit --base develop`: Dependabot resets the base back to
# `main` the next time it rebases the branch, and retargeting alone does not
# dispatch a CI run (it fires `edited`, not `synchronize`).

# Security updates always target the default branch; target-branch applies to version updates only.
updates:
# Python dependencies (pyproject.toml)
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "weekly"
target-branch: "develop"
labels:
- "dependencies"

# GitHub Actions
- package-ecosystem: "github-actions"
directory: "/"
schedule:
Expand All @@ -39,12 +17,10 @@ updates:
labels:
- "dependencies"
- "github-actions"

# VS Code extension (plugins/agentops/package.json)
- package-ecosystem: "npm"
directory: "/plugins/agentops"
schedule:
interval: "weekly"
target-branch: "develop"
labels:
- "dependencies"
- "dependencies"
Loading
Loading