Repository navigation
sieve 0.4.1 loads on every DSH 0.2.1 release from 0.2.1-rc.2 on. It fixes issue #7: 0.4.0 pinned its DSH peers to 0.2.1-rc.2, so DSH 0.2.1-rc.3 and later skipped it at startup and refused to install it. Nothing else changed.
Compatibility
- Both packages declare
engines.dsh>=0.2.1-rc.2 <0.2.2-0, and dsh-sieve's DSH peers use the same range. DSH readsengines.dshat install and startup. - Checked on DSH
0.2.1-rc.2to0.2.1-rc.5: none of the DSH packages sieve uses changed between them, and the packed plugin boots on rc.2 and rc.5. - DSH
0.2.2is not covered yet: its alpha reworks the tool pipeline sieve hooks into. pnpm release:packnow refuses to pack when the DSH on npm'slatestornexttag falls outsideengines.dsh.
Upgrade
dsh plugin --profile web add dsh-sieve@0.4.1 dsh-sieve-web@0.4.1Staying on 0.4.0 with a newer DSH? Accept the risk for one exact pair of versions: dsh plugin --profile <profile> allow-version dsh-sieve@0.4.0 --dsh-version <dsh --version> --accept-risk.
Or install from the tarballs below (check them against SHA256SUMS).