<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Tokenise</title><link>https://tokenise.rosvetic.com/categories/devops/</link><description>Recent content in DevOps on Tokenise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 08 Oct 2026 20:56:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/categories/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Have Claude write your team's morning digest with a read-only agent</title><link>https://tokenise.rosvetic.com/posts/claude-p-morning-digest/</link><pubDate>Thu, 08 Oct 2026 20:56:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/claude-p-morning-digest/</guid><description>&lt;p&gt;It&amp;rsquo;s 08:55. You open Teams to find out what happened on main overnight, and you do what everyone does: scroll the merge notifications, open four pull requests, read two titles that say &amp;ldquo;fixes&amp;rdquo; and give up on a third. Nobody asked you to do this. It&amp;rsquo;s just the tax for being the person who owns the service.&lt;/p&gt;</description></item><item><title>Let the agent cut the release, keep the approve button for yourself: npm staged publishing from Actions</title><link>https://tokenise.rosvetic.com/posts/npm-staged-publish-agent-release/</link><pubDate>Thu, 08 Oct 2026 16:03:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/npm-staged-publish-agent-release/</guid><description>&lt;p&gt;Picture the release step in a repo where a coding agent does a lot of the work. It bumps the version, writes the changelog from the merged PRs, opens the release PR. Then somebody has to publish, and the publish credential has to live somewhere the automation can reach it. That&amp;rsquo;s the part nobody loves: either a long-lived npm token in CI secrets, or a human at a laptop typing a one-time code.&lt;/p&gt;</description></item><item><title>Run Codex from a script: codex exec, structured output and CI</title><link>https://tokenise.rosvetic.com/posts/codex-exec-in-scripts-and-ci/</link><pubDate>Sun, 04 Oct 2026 07:00:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/codex-exec-in-scripts-and-ci/</guid><description>&lt;p&gt;Codex isn&amp;rsquo;t only a terminal app you sit in front of. &lt;code&gt;codex exec&lt;/code&gt; runs it without the interactive interface, so it can be a step in a script, a scheduled job or a CI pipeline. The &lt;a href="https://learn.chatgpt.com/docs/non-interactive-mode.md" target="_blank" rel="noopener noreferrer"&gt;non-interactive mode docs&lt;/a&gt;&#10; lay out the behavior, and the defaults tell you how OpenAI expects you to use it.&lt;/p&gt;</description></item><item><title>Cursor's Rollouts bot watches your deploys after the merge</title><link>https://tokenise.rosvetic.com/posts/cursor-rollouts-bot-watches-deploys/</link><pubDate>Tue, 29 Sep 2026 12:00:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/cursor-rollouts-bot-watches-deploys/</guid><description>&lt;p&gt;Cursor has added a bot called Rollouts that watches a change after it merges and reports whether it&amp;rsquo;s healthy in each environment. It was announced in the &lt;a href="https://cursor.com/changelog/rollouts-and-security-reviewer" target="_blank" rel="noopener noreferrer"&gt;Cursor changelog&lt;/a&gt;&#10; on September 23 and is available on Teams and Enterprise plans.&lt;/p&gt;</description></item></channel></rss>