5 posts tagged with "psake"

In psake projects, build.ps1 is the entry point script that wires everything together. It installs dependencies, configures the environment, and hands off to psake to run your actual build tasks. Think of it as the bootstrapper that gets a fresh machine — or a CI agent — from zero to a working build in a single command: .\build.ps1.

The default build.ps1 that ships with psake handles the basics well: bootstrap installation, help output, build environment detection, and proper CI exit codes. But once you're running concurrent CI jobs, managing internal package feeds, or onboarding new contributors, a few gaps start to show. Here are five patterns that harden your entry point for the real world.

We're thrilled to announce the v1.0 release of the psake VS Code extension—bringing first-class psake support directly into the world's most popular code editor. If you've been running psake from the terminal, you can now discover, navigate, and execute your build tasks without ever leaving VS Code.

Two exciting updates to share today: PowerShellBuild v0.8.0 has been released with built-in Authenticode code-signing support, and we've added a comprehensive PowerShellBuild documentation section right here on the psake docs site.

We're excited to announce the launch of the psake Agent Skill—a specialized knowledge package that enables AI coding assistants like Claude and GitHub Copilot to provide expert assistance with psake build automation tasks. Built on the open Agent Skills standard, this portable skill brings intelligent, context-aware guidance directly to your AI-assisted development workflow.

It's been a while since our last update, and we've got some exciting news to share! In this post, we'll cover recent releases, welcome new team members, and highlight the various initiatives we're working on to make psake even better.