For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/tutorials/daily-upgrades.md.
Docs
  • 26.11

    • Keep dependencies current

    This tutorial sets up a daily dependency check on Saleor. Atlas follows your team's upgrade policy, files the upgrades worth doing as work items, and takes the one you approve to a pull request. Pick a chapter to jump straight to it.

    What each chapter shows

    1. Teach Atlas your upgrade policy. Write how your team finds, ranks and tests upgrades as a skill, publish it with Publish in the Marketplace, and press Enable override to turn it on for the project. Read more in Marketplace.
    2. Schedule the daily check. In Automations, press New automation, pick Daily 09:00, write the instructions, check Repository, Shell commands and Web, and allow two work items and a Slack summary. Read more in Create an automation.
    3. Dry run, then switch it on. Press Dry run to see what the automation would do without acting, then switch it on and press Run now.
    4. Today's run. Open the run to read its summary and outputs: one work item per upgrade and one notification, which also lands in Slack. Read more in Runs and history.
    5. Approve an upgrade. Open an upgrade work item on the board, read Atlas's triage and plan, and press Approve plan. Read more in Work the board.
    6. Review the pull request. Read the change summary, the files it changed and the test runs the platform repeated, then merge it when you are ready.