v7.6.0

Features

• #1746 support pause and resume for transactional send journeys by @JoernBerkefeld in #1765
• #1919 reroute stop journey to pause journey for transactional send journeys because these don't support stop by @JoernBerkefeld in #1920
• #1921 allow updating emails for selected journeys using the refresh command (transactional + multi-step) by @JoernBerkefeld in #1922
• #1879 Allow stopping all versions of a multi-step journey by @JoernBerkefeld in #1929

Bugfixes

• #1881 handle bad journey retrieve-by-key responses gracefully by @JoernBerkefeld in #1887
• #1774 show proper error when no keys were provided to build / bt / bd / bdb by @JoernBerkefeld in #1888
• #1889 throttle refresh to 10 concurrent triggeredSends/journeys to avoid timeouts; add icons for pause/publish/start by @JoernBerkefeld in #1890
• #1914 make dataExtension-not-found error easier to understand when trying to delete by @JoernBerkefeld in #1915
• #1916 keys with ":" in could not be found before by @JoernBerkefeld in #1917
• #1836 Ensure automatic new version creation during deploy only happens to multi-step jourmeys without a draft version - but not for transactional send journeys which are not versioned by @JoernBerkefeld in #1930
• #1837 deleting transactional send journey no longer asks for a version by @JoernBerkefeld in #1931

Chores

• #1882 set maxKeyLength for journey and transactionalEmail by @JoernBerkefeld in #1883
• #1880 hint to using --ignoreSfFields / --isf to skip deploy error by @JoernBerkefeld in #1886

Dependencis

• Bump winston from 3.15.0 to 3.17.0 by @dependabot in #1871
• Bump @eslint/js from 9.10.0 to 9.15.0 by @dependabot in #1875
• Bump husky from 9.1.6 to 9.1.7 by @dependabot in #1872
• Bump chai from 5.1.1 to 5.1.2 by @dependabot in #1873
• Bump eslint from 9.10.0 to 9.15.0 and eslint-plugin-unicorn from 56.0.0 to 56.0.1 by @dependabot in #1874
• Bump eslint-plugin-jsdoc from 50.5.0 to 50.6.1 by @dependabot in #1937
• Bump @types/node from 22.9.0 to 22.10.2 by @dependabot in #1936
• Bump eslint from 9.15.0 to 9.17.0 by @dependabot in #1935
• Bump globals from 15.12.0 to 15.14.0 by @dependabot in #1938
• Bump @eslint/js from 9.15.0 to 9.17.0 by @dependabot in #1934
• Bump prettier from 3.3.3 to 3.4.2 by @dependabot in #1925
• Bump typescript from 5.6.3 to 5.7.2 by @dependabot in #1895
• Bump mocha from 10.7.3 to 11.0.1 by @dependabot in #1912
• Bump conf from 13.0.1 to 13.1.0 by @dependabot in #1926

Full Changelog: v7.5.0...v7.6.0

Details

Standard Commands

refresh

Command: mcdev refresh <business unit> [type] [external key] [--metadata]

Alias: mcdev re

This command lets you refresh emails in journeys and triggeredSends to ensure that updates made to the email or loaded content blocks get reflected when the emails are send out. This is only relevant is your journey is already "running" / your triggeredSend is "active".

If you do not specify keys, for triggeredSend, it will refresh all running ("Active") triggered sends on the given BU. It will also check if all dependencies for that triggered send are available to ensure it can be published & restarted after it was paused. However, if you made changes to the email that caused issues, you might still get an error, which prevents you from restarting it.

Currently supported types:

Name	CLI Argument	Effect
Triggered Send	triggeredSend	Refreshes emails in active triggeredSends and, thereby, any emails in Journeys.
Journey	journey	Refreshes emails in multi-step journeys (by refreshing associated triggered sends) and transactional send journeys.

Refreshing a multi-step journey will not be reflected in the journey's 'json. However, if you refresh a transactional send journey, it will affect the last modified date.

Example:

mcdev refresh MyProject/_ParentBU_ -m triggeredSend
mcdev refresh MyProject/_ParentBU_ -m triggeredSend:myTsKey

mcdev refresh MyProject/_ParentBU_ -m journey:key1 journey:key2

stop

Command: mcdev stop <business unit> [type] [key] [--like] [--metadata]

Alias: -

This command lets you stop metadata of a given type and key.

Currently supported types:

Name	CLI Argument	Effect
Journey	journey	stops running journey

For journeys you can choose to specify a specific version to stop by appending "/4" (to stop version 4). If you do not append a version, mcdev will attempt to stop the latest version. Alternatively, you can stop all versions by appending "/*".

Example (stopping highest version):

mcdev stop MyProject/DEV -m journey:keyA journey:keyB journey:keyC

Example (stopping specific version):

mcdev stop MyProject/DEV -m journey:keyA/3 journey:keyB/2

Example (stopping all versions):

mcdev stop MyProject/DEV -m journey:keyC/*

stop with --like operator:

Instead of specifying a key, you can use the --like option to find your target. This is equal to not specifying a version and will default to the highest version.

mcdev stop MyProject/DEV -m journey --like.key "myprefix_%"
mcdev stop MyProject/DEV -m journey --like.key "myprefix_%" --like.r__folder_Path "my Journeys/Testing%"

stop on all BUs:

This variation of the stop command allows you to stop specified items on all BUs. mcdev will look for the items of defined types and keys on all BUs and stop them.

Example:

mcdev stop MyProject/* -m journey:keyA journey:keyB
mcdev stop MyProject/* -m journey:keyA/2 journey:keyB/3
mcdev stop MyProject/* -m journey:keyA/* journey:keyB/*