A git tag is how many teams mark a release as ready. Pulumi Deployments can now act on that signal directly: configure a tag-based trigger, push a version tag like v1.2.0, and Pulumi automatically runs pulumi up for your stack. No extra pipeline glue, no manual click — your release tag is the deployment.

Why tags?

Push to Deploy has long let you preview changes on a pull request and update a stack when commits merge to a branch. That branch-based model is a great fit for continuous delivery to shared development and QA environments, where every merge should flow straight through.

But promotion to production is often deliberate, not continuous. You merge throughout the day, then decide — separately — that a particular commit is the release. The conventional way to record that decision is a git tag: v1.2.0, 2026.06.0, release-2026-06-04. Tagging is already part of most teams’ release rituals.

Tag-based triggers connect that ritual to your infrastructure. Instead of wiring up a separate CI job to call the Pulumi Deployments REST API on a tag event, you configure the trigger once in your stack’s deployment settings and let Pulumi handle the rest.

How it works

Tag triggers are controlled by two settings on your stack’s deployment configuration:

• Run updates for pushed tags — a toggle that enables running pulumi up when a matching tag is pushed.
• Tag filters — a list of glob patterns that decide which tag names qualify.

Tag filters use the same model as the path filters you may already know, except the patterns match against the tag name rather than changed file paths. A few examples:

• v* — deploy on any tag beginning with v, such as v1.0.0 and v2.3.1.
• v* plus !*-rc* — deploy on release tags but skip release candidates like v1.2.0-rc1.
• 2026.* — deploy on calendar-versioned releases such as 2026.06.0.

Filters prefixed with ! are exclusions, and an exclusion always wins over an include. With no filters configured and the toggle on, every tag push deploys. Deleting a tag never triggers a deployment.

When a tag push kicks off a deployment, Pulumi sets the PULUMI_CI_TAG_NAME environment variable to the tag name. Your pre-run commands or your Pulumi program can read it — for example, to stamp the release version onto a resource tag or an application config value.

Works across every VCS integration

Tag triggers are available across all five version control integrations: GitHub, GitLab, Bitbucket, Azure DevOps, and Custom VCS.

Get started

You can configure tag triggers wherever you manage deployment settings today — the Pulumi Cloud console, the REST API, or as code with the pulumiservice.DeploymentSettings resource.

To try it out:

1. Open a stack’s Settings > Deploy tab in the Pulumi Cloud console.
2. Enable Run updates for pushed tags and add a tag filter such as v*.
3. Push a tag — git tag v1.0.0 && git push origin v1.0.0 — and watch the deployment run.

For the full details, see the deployment triggers and tag filtering documentation. We’d love to hear how you put tag-based deployments to work.

In an era where artificial intelligence can not only execute but generate code, the role of software engineers is undergoing a significant transformation. Tom Enden’s tech talk, The End of Determinism: What’s Left for Engineers When AI Writes the Code, presented at the Wix Engineering Tech Talks, delves into the philosophical implications of this shift.

A Confession and a Paradigm Shift

Based on content from Wix Engineering Tech Talks

The talk begins with a striking confession: Enden shipped code he didn’t fully understand, in a language he wasn’t fluent in, and paradoxically, he felt proud of it. This scenario, once unimaginable, now captures a prevailing sentiment among engineers.

As we pivot from the deterministic world—where every input precisely corresponds to a coded output—towards generative AI-driven solutions, the foundation of software engineering feels unsettled. The core question arises: What becomes of the engineer’s identity when AI assumes the role of coding?

The Engineer’s New Skillset

Rather than signalling an end, this transformation elevates the profession to higher realms of complexity and nuance. According to Enden, three pivotal skills emerge:

• Dialogue: Coding has turned Socratic as engineers learn to ask the right questions instead of asserting predetermined answers.
• Ownership: While authorship of code becomes distributed among humans and machines, ownership remains a vital, human responsibility.
• Taste & Judgment: In a landscape wrought with uncertainty, recognizing valuable solutions and committing to them becomes paramount.

Beyond the Code: Towards a Philosophical Engineering Practice

Echoing Emeritus Uncles of Code, like Bob Martin, who tout the irrelevance of syntax, Enden argues that syntax has always been mere scaffolding, allowing engineers to address more substantive problems. Climbing the ladder of abstraction historically has led us to more intellectually engaging challenges, and now, we must confront the ultimate abstraction: a philosophical approach to engineering.

Understanding Authorship and Ownership

In a world where AI collaborates with humans, authorship appears complex and interconnected, echoing Roland Barthes’s assertion that any text is a tissue of quotations. Engineers must redefine their role—not as sole authors, but as custodians who ensure the reliability and integrity of AI-generated work. This notion of ownership is framed by the responsibility to address and rectify issues arising from AI-developed code, transforming engineers from mere coders into knowledgeable stewards.

Cultivating Taste and Judgment

As Greg Brockman of OpenAI suggests, taste—an engineer’s sense of distinguishing quality—becomes a key skill. Historical discourses, like those of Steve Jobs, recognize taste as a cornerstone in innovation, now more significant than ever. Engineers are tasked with discerning what to pursue among myriad possibilities AI presents—thus enacting judgment that steers technological development.

Conclusion: The Philosopher-Engineer

This philosophically driven engineering practice suggests that while the means of creation have evolved, the essence of engineering—embracing complexity and exerting discernment—remains constant, if not more pronounced. As the dust settles around AI and code generation, we rediscover ourselves as philosophers of technology, negotiating the fine line between capability and consequence.

The transformation ultimately challenges engineers to ponder not only their craft but also the driving forces and ethical dimensions behind it. In answering the final question Enden poses—“Who made this presentation?”—we recognize the intricate web of human and AI interaction shaping our shared digital future.

[Audience applause]

In this post, we explore seven simple reasons why you should write a memoir and why your life story matters and is worth telling.

If you have decided to write about your life, you have made a decision to write a memoir. Remember that this is not an easy journey, and you will wonder why you are doing it many times. If you can work through this, you will accomplish something special. As William Zinsser says: ‘Memoir isn’t the summary of a life; it’s a window into a life, very much like a photograph in its selective composition. It may look like a casual, and even random, calling up of bygone events. It’s not; it’s a deliberate construction.’

7 Really Good Reasons To Write A Memoir

The most important reason to write a memoir:

There are many reasons for writing your life story, but the most compelling one is this:

1. To Tell Your Story – Only you can tell your story your way. Other writers cannot write it the way you want to write it. You have something special – your voice and your style. As Diana Raab says: ‘When you write a memoir, you are writing your version of what you think happened from your own perspective. Someone else might have another version. ’

Other important reasons to write about yourself:

2. To Make Sense Of Your Life. Memoirists often write to tell other people what happened to them, but they end up learning more about themselves in the process.

3. To Release The Pain. Memoirists write as therapy. If they write the truth, in their own voices, a memoir can be a healing experience. According to Anne Lamott: “You own everything that happened to you. Tell your stories. If people wanted you to write warmly about them, they should have behaved better.”

4. To Leave A Record. Memoirists are adding to the tapestry of life. Writing down your experiences means that you are adding to the recorded history of the world.

5. To Leave A Trail. Memoirists are offering their families and friends their side of the story. Even if they are never published in the greater world, they will have left a trail for people who knew them to follow.

6. To Connect. Memoirists become part of a community when they tell their stories. They are able to connect with people who have gone through a similar experience or with people who have not, but who can empathise and learn from their stories. As Isabel Allende explains: ‘I have more freedom when I write fiction, but my memoirs have had a much stronger impact on my readers. Somehow the ‘message’, even if I am not even aware that there is one, is conveyed better in this form.’

7. To Learn How To Tell Stories. The craft of storytelling is a great one for anybody to have in this life. Memoirists learn how to create stories and scenes with beginnings, middles, and endings. They learn how to organise their thoughts and to communicate more clearly.

The Last Word

Don’t write a memoir to get revenge or to teach people a lesson. Write it for yourself. If they learn something from your book, that is a bonus. So learn how to write, construct a story framework that makes sense, and finish writing your memoir.

Top Tip: If you want to learn how to write a memoir, look into our Secrets of a Memoirist course.

by Amanda Patterson
© Amanda Patterson

If you liked this blogger’s writing, you may enjoy:

1. The Ultimate Checklist For Writing A Memoir
2. How To Find Your Story’s Theme In 3 Simple Steps
3. Why Embracing Your Inner Madness Makes You A Better Writer
4. What Is A Story Goal? The Secret To A Strong Plot
5. 45 Ways To Avoid Using The Word ‘Very’
6. What Is Tone? 155 Words To Describe An Author’s Tone
7. What Is Direct & Indirect Characterisation? & Which One Should I Use?
8. 20 Fun Ways To Find Plot Ideas For Your Story
9. All About Pacing: 4 Key Questions Every Writer Should Ask
10. Past Tense Or Present Tense: Which Works Best For Your Story?

Top Tip: Sign up for our free daily writing links

The post 7 Really Good Reasons To Write A Memoir appeared first on Writers Write.

Discover 15 inspiring reasons to start writing poetry, from boosting creativity and experimentation to strengthening your voice and improving your overall writing skills.

Why should you write poems?

Because they’re awesome, but also because poetry is even more condensed than the short story. I find writing poems challenging, and they make me approach writing differently.

15 Inspiring Reasons To Start Writing Poetry

They also:

1. Allow you to brainstorm. Because the medium differs from stories, poems allow you to express things differently. Use them to brainstorm ideas.
2. Make your words work. Even more than the short story, poems have limited words, and we need to make our words work hard.
3. Make you think differently about words. Poems make us re-evaluate words and think of new ways to manipulate language.
4. Make you evaluate each word, because the condensed nature of a poem means we have to spend even more time evaluating our word choice.
5. Allow you to say exactly what it is you want to say. Poems act as a filter and help us get to the guts of the matter.
6. Have rules, but they also have no rules. You get to break all the rules when you write poems but do it only because it serves the poem. Manipulate grammar, change the sentence structure.
7. Allow you to experiment and experiment some more. Have fun.
8. Have many places to submit. The only thing there is more of on the internet than short story competitions and submissions are poetry sites. Dig in.
9. Are even quicker to write. A poem can take a few minutes and just spill out or it can take years.
10. Give you a break from fiction, because it is such a different medium.
11. Make you more aware of how words and sentences sound, which will improve your fiction.
12. Help you express emotion and feelings. Poems are supposed to make you feel something even if you don’t understand them. They help you get feelings out.
13. Give you deadlines, deadlines, and more deadlines. Find them online, sign up here, but get going.
14. Give you an opportunity to learn by reading and commenting on other poems.
15. Help you learn from the comments and feedback from other poets.

It is true that many of these are applicable of all writing, but I hope that I have convinced you that poems are valuable. These 15 reasons to write poetry should inspire you. It would be awesome if you would like to join us for this new adventure on the 12 Poems Challenge.

Read my Poetry 101 Series:

1. Poetry 101: What Is A Poem?
2. Poetry 101: How To Analyse A Poem
3. Poetry 101: Creating Figurative Language Using Literary Devices
4. Poetry 101: Kinds Of Poems – The Sonnet
5. Poetry 101: Kinds Of Poems – The Haiku
6. Poetry 101: Kinds Of Poems – Free Verse
7. Poetry 101: Kinds Of Poems – The Limerick
8. Poetry 101: Kinds Of Poems – The Villanelle
9. Poetry 101: Kinds Of Poems: The Ballad

by Mia Botha

If you enjoyed this blogger’s writing, you will love:

1. Worldbuilding: The Ultimate Setting Checklist For Writers
2. Show Don’t Tell: 5 Simple Techniques Every Writer Should Know
3. How To Show & Not Tell In Short Stories
4. A Complete Guide To Writing Prompts & Daily Writing Practice
5. How To Write What You Love
6. 4 Point Of View Choices For Writers
7. Where Does Conflict Come From In Fiction?
8. Writing Competitions To Inspire You
9. How To Write Epic Beginnings
10. How Much Magic Do You Need In A Fantasy Novel?

Top Tip: Sign up for our free daily writing links.

The post 15 Inspiring Reasons To Start Writing Poetry appeared first on Writers Write.

Update kernel to 6.18.33.1-1 (#40728)