Repository navigation
Releases: haskou/flow
Release list
v3.0.2
v3.0.1
Changes
- fix(ci): 🐛 Drop registry-url from publish job for setup-node v7
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/3.0.1
- Pull request: #56
- Source branch:
fix/publish-setup-node-v7 - Version bump:
patch
Pull request notes
setup-node v7 ya no exporta un NODE_AUTH_TOKEN ficticio (actions/setup-node#1558). Con registry-url + cache: yarn, yarn 1 falla con Failed to replace env in config: ${NODE_AUTH_TOKEN} y el job Publish to npm no llega a publicar. La publicación usa OIDC (id-token: write), así que registry-url no hace falta.
v3.0.0
Changes
- fix(deps)!: 🐛 Update dependencies and install repository skills
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/3.0.0
- Pull request: #44
- Source branch:
break/update-dependencies - Version bump:
major
Pull request notes
Sustituye #43 para publicar el cambio mediante la ruta major de la rama break/update-dependencies.
Actualiza @haskou/value-objects de 2.13.1 a 7.0.2 y Prettier de 3.9.6 a 3.9.7. Instala las cinco skills de haskou/ddd-engineer-skills con su instalador npx y registra versiones y hashes. TypeScript permanece en 6.0.3 por compatibilidad con ESLint y ts-jest.
BREAKING CHANGE: isEqual() exige el mismo tipo concreto de Value Object. Para comparar duraciones entre tipos se utiliza hasValue(). Los consumidores deben actualizar su dependencia directa de @haskou/value-objects a 7.x y compartir la misma instancia del paquete con Flow; las instancias de Duration de una instalación distinta no pasan la normalización instanceof. Los milisegundos numéricos siguen admitidos. La documentación incluye la guía de migración.
Validación local: lint y 98 tests, tsc --noEmit, build de librería y documentación correctos. Las tres aserciones afectadas usan el nuevo contrato hasValue().
v2.0.1
Changes
- fix(renovate): 🐛 Stop release-prefixed dependency branches
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/2.0.1
- Pull request: #10
- Source branch:
fix/publish-from-pr-title - Version bump:
patch
Pull request notes
What changed
- Updated Renovate config so dependency branches no longer get release-driving prefixes such as
break/,fix/, orchore/. - Removed
branchPrefix,branchPrefixOld, and the package-ruleadditionalBranchPrefixvalues.
Why
Renovate produced major-update branches such as break/actions-checkout-7.x while keeping the PR title as chore(deps). The problem is the Renovate branch naming config: dependency maintenance branches should not encode release intent.
The publish workflow remains unchanged. Release behavior continues to be controlled by the branch naming contract used by humans, while Renovate no longer generates branches that accidentally match that contract.
Validation
renovate.jsonparses as valid JSON.yarn lintyarn build
v2.0.0
Changes
- chore(deps): ⬆️ update actions/configure-pages action to v6
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/2.0.0
- Pull request: #9
- Source branch:
break/actions-configure-pages-6.x - Version bump:
major
Pull request notes
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| actions/configure-pages | action | major | v4 → v6 |
Release Notes
actions/configure-pages (actions/configure-pages)
v6.0.0
Changelog
- upgrade to node 24 @salmanmkc (#186)
- Upgrade IA Publish @Jcambass (#165)
- Add workflow file for publishing releases to immutable action package @Jcambass (#163)
- pin draft release version @YiMysty (#162)
- Bump espree from 9.6.1 to 10.1.0 @dependabot (#160)
- Bump eslint-config-prettier from 8.8.0 to 9.1.0 @dependabot (#143)
- Be more friendly to Dependabot @yoannchaudet (#158)
- Bump eslint-plugin-github from 4.10.2 to 5.0.1 @dependabot (#154)
- Bump braces from 3.0.2 to 3.0.3 in the npm_and_yarn group @dependabot (#156)
- Bump undici from 5.28.3 to 5.28.4 @dependabot (#145)
See details of all code changes since previous release.
v6
v5.0.0
Breaking Changes
- When using the input param
static_site_generator: next:- Added support for Next.js >= 13.3.0
- Consequently, also dropped support for Next.js < 13.3.0
Full Changelog
- Attempt to auto-detect configuration files with varying file extensions @JamesMGreene (#139)
- Convert errors into Actions-compatible logging with annotations @JamesMGreene (#138)
- Bump @actions/github from 5.1.1 to 6.0.0 @dependabot (#123)
- Bump the non-breaking-changes group with 2 updates @dependabot (#136)
- Update the Next.js configuration for v14 @JamesMGreene (#137)
- Bump the non-breaking-changes group with 3 updates @dependabot (#132)
- Bump release-drafter/release-drafter from 5 to 6 @dependabot (#133)
- Bump github/codeql-action from 2 to 3 @dependabot (#127)
- Bump actions/checkout from 3 to 4 @dependabot (#120)
- Bump actions/setup-node from 3 to 4 @dependabot (#118)
- Bump the non-breaking-changes group with 1 update @dependabot (#131)
- Update Dependabot config to group non-breaking changes @JamesMGreene (#130)
See details of all code changes since previous release.
v5
Configuration
📅 Schedule: (in timezone Europe/Madrid)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
v1.0.0
Changes
- chore(deps): ⬆️ update actions/checkout action to v7
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/1.0.0
- Pull request: #8
- Source branch:
break/actions-checkout-7.x - Version bump:
major
Pull request notes
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| actions/checkout | action | major | v5 → v7 |
| actions/checkout | action | major | v4 → v7 |
Release Notes
actions/checkout (actions/checkout)
v7.0.0
- Block checking out fork PR for pull_request_target and workflow_run by @aiqiaoy in #2454
- Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @dependabot[bot] in #2458
- Bump flatted from 3.3.1 to 3.4.2 by @dependabot[bot] in #2460
- Bump js-yaml from 4.1.0 to 4.2.0 by @dependabot[bot] in #2461
- Bump @actions/core and @actions/tool-cache and Remove uuid by @dependabot[bot] in #2459
- upgrade module to esm and update dependencies by @aiqiaoy in #2463
- Bump the minor-npm-dependencies group across 1 directory with 3 updates by @dependabot[bot] in #2462
v7
- Block checking out fork PR for pull_request_target and workflow_run by @aiqiaoy in #2454
- Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @dependabot[bot] in #2458
- Bump flatted from 3.3.1 to 3.4.2 by @dependabot[bot] in #2460
- Bump js-yaml from 4.1.0 to 4.2.0 by @dependabot[bot] in #2461
- Bump @actions/core and @actions/tool-cache and Remove uuid by @dependabot[bot] in #2459
- upgrade module to esm and update dependencies by @aiqiaoy in #2463
- Bump the minor-npm-dependencies group across 1 directory with 3 updates by @dependabot[bot] in #2462
v6.0.3
- Fix checkout init for SHA-256 repositories by @yaananth in #2439
- fix: expand merge commit SHA regex and add SHA-256 test cases by @yaananth in #2414
v6.0.2
- Fix tag handling: preserve annotations and explicit fetch-tags by @ericsciple in #2356
v6.0.1
- Add worktree support for persist-credentials includeIf by @ericsciple in #2327
v6.0.0
- Persist creds to a separate file by @ericsciple in #2286
- Update README to include Node.js 24 support details and requirements by @salmanmkc in #2248
v6
- Fix checkout init for SHA-256 repositories by @yaananth in #2439
- fix: expand merge commit SHA regex and add SHA-256 test cases by @yaananth in #2414
v5.0.1
- Port v6 cleanup to v5 by @ericsciple in #2301
Configuration
📅 Schedule: (in timezone Europe/Madrid)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
v0.1.2
Changes
- fix(ci): 🐛 Use main for workflows and add license
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/0.1.2
- Pull request: #7
- Source branch:
fix/pages-main-license - Version bump:
patch
Pull request notes
What changed
- Updated the GitHub Pages workflow to run from
maininstead ofmaster. - Removed the remaining
masterreferences from the CI workflow branch filters and publish condition. - Added the missing
LICENSE.txtfile with the MIT license text. - Formatted
FallbackAttemptto satisfy the current lint rules onmain.
Why
The repository default branch is main, so workflows should not depend on master. The README and package.json also reference MIT licensing, but the actual license file was missing.
Validation
yarn lintyarn buildyarn test:coverageyarn docs:build- Confirmed there are no remaining
masterreferences in.github, docs, README, orpackage.json.
v0.1.1
Changes
- fix(flow): 🐛 Harden fallback and cancellation behavior
Release details
- npm: https://www.npmjs.com/package/@haskou/flow/v/0.1.1
- Pull request: #6
- Source branch:
fix/prepublish-flow-hardening - Version bump:
patch
Pull request notes
What changed
- Fixed
FallbackChainso0,false, and""are treated as valid resolved values. - Changed
FallbackChainto propagate errors by default, with explicit best-effort mode throughFallbackChainOptions.catchingErrors()and.onError(). - Ensured
TimeoutandAbortableclean up timers/listeners when work settles. - Made
Retrierdelays abortable between attempts. - Added cancellable waiters to
Semaphore.acquire(signal). - Fixed the publish workflow so the first npm publish does not fail when the package does not exist yet.
- Updated documentation and README badges.
Why
The prepublish review was right on the important issues: falsy values were incorrectly treated as fallback misses, errors were silently swallowed by default, timers/listeners could stay alive longer than needed, and the first publish could fail before npm had any published version for the package.
Validation
yarn lintyarn buildyarn test:coveragewith 100% coverageyarn docs:build