## Summary
- Changes all 11 dependabot entries from `weekly` to `monthly` schedule
to reduce PR noise
- Removes `day: monday` (only valid for weekly cadence)
- Adds `update-types` split to every entry so breaking major upgrades
arrive in a separate PR from safe minor/patch updates
**Before:** one wildcard group, weekly, major and minor/patch mixed
together
**After:** two groups (`minor-and-patch` / `major`), monthly
## Test plan
- [x] Confirm dependabot picks up the new config (check Insights →
Dependency graph → Dependabot)
- [ ] Verify next scheduled run produces two grouped PRs per ecosystem
(minor+patch bundle, major bundle) rather than one-per-dep
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Add some conformance tests for checkpointer implementations. Includes
additona methods that will be useful if you want to integarte in the
agent server.
- Add schedule.day: monday to all entries
- Add groups configuration to prevent noisy per-dependency PRs
- Split pip directories into individual entries per Dependabot v2 spec
- Add npm ecosystem entries for js-examples and js-monorepo-example
subdirectories
- Specify package-manager: uv for all Python entries (repo uses uv.lock)
Thank you for contributing to LangGraph! Follow these steps to mark your
pull request as ready for review. **If any of these steps are not
completed, your PR will not be considered for review.**
- [x] **PR title**: Follows the format: {TYPE}({SCOPE}): {DESCRIPTION}
- Examples:
- feat(core): add multi-tenant support
- fix(cli): resolve flag parsing error
- docs(openai): update API usage examples
- Allowed `{TYPE}` values:
- feat, fix, docs, style, refactor, perf, test, build, ci, chore,
revert, release
- Allowed `{SCOPE}` values (optional):
- langgraph, docs, cli, checkpoint, checkpoint-postgres,
checkpoint-sqlite, prebuilt, scheduler-kafka, sdk-py
- Once you've written the title, please delete this checklist item; do
not include it in the PR.
- [x] **PR message**: ***Delete this entire checklist*** and replace
with
- **Description:** a description of the change. Include a [closing
keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
if applicable.
- **Issue:** the issue # it fixes, if applicable
- **Dependencies:** any dependencies required for this change
- **Twitter handle:** if your PR gets announced, and you'd like a
mention, we'll gladly shout you out!
- [x] **Add tests and docs**: If you're adding a new integration, you
must include:
1. A test for the integration, preferably unit tests that do not rely on
network access,
2. An example notebook showing its use. It lives in
`docs/docs/integrations` directory.
- [x] **Lint and test**: Run `make format`, `make lint` and `make test`
from the root of the package(s) you've modified. We will not consider a
PR unless these three are passing in CI. See [contribution
guidelines](https://docs.langchain.com/oss/python/contributing/overview)
for more.
Additional guidelines:
- Make sure optional dependencies are imported within a function.
- Please do not add dependencies to `pyproject.toml` files (even
optional ones) unless they are **required** for unit tests.
- Most PRs should not touch more than one package.
- Changes should be backwards compatible.
