Skip to content

Releases: TatuHQ/TatuTime

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 26 Oct 23:26
426fcd7

Release-coverage note. The crate version at this commit is 0.2.1 and no earlier commit has tagged it, so this commit is released as v0.2.1.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore: require owner approval for changes to main by @ECiurleo in #434
  • chore: sync AgentRules from TatuAgentRules by @ECiurleo in #435
  • chore(deps): refresh toolchain, Rust crates, Node and CI tooling by @ECiurleo in #436

Full Changelog: v0.2.0...v0.2.1

v0.2.0+56b8d87

Choose a tag to compare

@github-actions github-actions released this 26 Oct 14:06
56b8d87

Release-coverage note - why this tag carries build metadata. No version bump landed with this commit: Cargo.toml still reads version 0.2.0, and v0.2.0 is already tagged on the earlier commit 38fc1e7. A tag is never moved or rewritten here, so rather than leave this commit unreleased - the gap the v0.1.8 notes record by hand for the uuid (#285) and serde_json (#347) bumps - it is released as v0.2.0+56b8d87, whose +56b8d87 suffix is semver build metadata identifying the commit.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore: sync AgentRules from TatuAgentRules by @ECiurleo in #435

Full Changelog: v0.2.0+1e20e8a...v0.2.0+56b8d87

v0.2.0+1e20e8a

Choose a tag to compare

@github-actions github-actions released this 26 Oct 13:27
1e20e8a

Release-coverage note - why this tag carries build metadata. No version bump landed with this commit: Cargo.toml still reads version 0.2.0, and v0.2.0 is already tagged on the earlier commit 38fc1e7. A tag is never moved or rewritten here, so rather than leave this commit unreleased - the gap the v0.1.8 notes record by hand for the uuid (#285) and serde_json (#347) bumps - it is released as v0.2.0+1e20e8a, whose +1e20e8a suffix is semver build metadata identifying the commit.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore: require owner approval for changes to main by @ECiurleo in #434

Full Changelog: v0.2.0...v0.2.0+1e20e8a

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 01:40
38fc1e7

Release-coverage note. The crate version at this commit is 0.2.0 and no earlier commit has tagged it, so this commit is released as v0.2.0.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore: rebrand as TatuHQ TatuTime by @ECiurleo in #432
  • fix(ci): give the release job its own scratch directory by @ECiurleo in #433

Full Changelog: v0.1.78...v0.2.0

v0.1.78

Choose a tag to compare

@github-actions github-actions released this 23 Oct 21:28
6c52e11

Release-coverage note. The crate version at this commit is 0.1.78 and no earlier commit has tagged it, so this commit is released as v0.1.78.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • fix(web): serve brand PNGs with an image MIME type by @ECiurleo in #429

Full Changelog: v0.1.77...v0.1.78

v0.1.77

Choose a tag to compare

@github-actions github-actions released this 23 Oct 21:10
c18c81d

Release-coverage note. The crate version at this commit is 0.1.77 and no earlier commit has tagged it, so this commit is released as v0.1.77.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • feat(gui): carry the Tucano Technology brand into the app by @ECiurleo in #428

Full Changelog: v0.1.76...v0.1.77

v0.1.76

Choose a tag to compare

@github-actions github-actions released this 23 Oct 19:14
53786a3

Release-coverage note. The crate version at this commit is 0.1.76 and no earlier commit has tagged it, so this commit is released as v0.1.76.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore(deps): bump distroless/cc-debian13 from e792ab3 to 83b9b50 by @dependabot[bot] in #420
  • chore(deps): bump jsdom from 30.1.2 to 30.1.3 in /gui-test by @dependabot[bot] in #421
  • chore(deps): bump sass from 1.105.1 to 1.105.2 in /gui-test by @dependabot[bot] in #422
  • feat(gui): filter customers, projects and tasks by status by @ECiurleo in #427

Full Changelog: v0.1.75...v0.1.76

v0.1.75+c3b4674

Choose a tag to compare

@github-actions github-actions released this 23 Oct 18:31
c3b4674

Release-coverage note - why this tag carries build metadata. No version bump landed with this commit: Cargo.toml still reads version 0.1.75, and v0.1.75 is already tagged on the earlier commit 2191f9c. A tag is never moved or rewritten here, so rather than leave this commit unreleased - the gap the v0.1.8 notes record by hand for the uuid (#285) and serde_json (#347) bumps - it is released as v0.1.75+c3b4674, whose +c3b4674 suffix is semver build metadata identifying the commit.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore(deps): bump distroless/cc-debian13 from e792ab3 to 83b9b50 by @dependabot[bot] in #420

Full Changelog: v0.1.75...v0.1.75+c3b4674

v0.1.75+3fb2c8d

Choose a tag to compare

@github-actions github-actions released this 23 Oct 18:54
3fb2c8d

Release-coverage note - why this tag carries build metadata. No version bump landed with this commit: Cargo.toml still reads version 0.1.75, and v0.1.75 is already tagged on the earlier commit 2191f9c. A tag is never moved or rewritten here, so rather than leave this commit unreleased - the gap the v0.1.8 notes record by hand for the uuid (#285) and serde_json (#347) bumps - it is released as v0.1.75+3fb2c8d, whose +3fb2c8d suffix is semver build metadata identifying the commit.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore(deps): bump sass from 1.105.1 to 1.105.2 in /gui-test by @dependabot[bot] in #422

Full Changelog: v0.1.75+0c60ae3...v0.1.75+3fb2c8d

v0.1.75+0c60ae3

Choose a tag to compare

@github-actions github-actions released this 23 Oct 18:44
0c60ae3

Release-coverage note - why this tag carries build metadata. No version bump landed with this commit: Cargo.toml still reads version 0.1.75, and v0.1.75 is already tagged on the earlier commit 2191f9c. A tag is never moved or rewritten here, so rather than leave this commit unreleased - the gap the v0.1.8 notes record by hand for the uuid (#285) and serde_json (#347) bumps - it is released as v0.1.75+0c60ae3, whose +0c60ae3 suffix is semver build metadata identifying the commit.

Release scheme. The crate version in Cargo.toml is the release version, bumped inside the PR that lands on main. .github/workflows/release.yml runs on every push to main and releases the commit it is given; when v<version> is already tagged at another commit, the commit is identified with semver build metadata, v<version>+<short-sha>, instead, so no commit that lands on main can go unreleased.

What's Changed

  • chore(deps): bump jsdom from 30.1.2 to 30.1.3 in /gui-test by @dependabot[bot] in #421

Full Changelog: v0.1.75+c3b4674...v0.1.75+0c60ae3