Release for v0.1.6 by Rindrics · Pull Request #94 · Rindrics/slackmail

Rindrics · 2026-02-09T19:25:19Z

This pull request is for the next release as v0.1.6 created by tagpr. Merging it will tag v0.1.6 to the merge commit and create a GitHub release.

You can modify this branch "tagpr-from-v0.1.5" directly before merging if you want to change the next version number or other files for the release.

How to change the next version as you like

There are two ways to do it.

Version file
- Edit and commit the version file specified in the .tagpr configuration file to describe the next version
- If you want to use another version file, edit the configuration file.
Labels convention
- Add labels to this pull request like "tagpr:minor" or "tagpr:major"
- If no conventional labels are added, the patch version is incremented as is.

What's Changed

build(deps-dev): bump vite-tsconfig-paths from 6.0.3 to 6.0.4 by @dependabot[bot] in build(deps-dev): bump vite-tsconfig-paths from 6.0.3 to 6.0.4 #89
chore: enhance Husky hooks with comprehensive validation by @Rindrics in chore: enhance Husky hooks with comprehensive validation #93
feat: support single-user- multi-domain- usecase by @Rindrics in feat: support single-user- multi-domain- usecase #92
Revert "feat: support single-user- multi-domain- usecase" by @Rindrics in Revert "feat: support single-user- multi-domain- usecase" #95
ci: resolve AWS auth error for dependabot by @Rindrics in ci: resolve AWS auth error for dependabot #97
build(deps-dev): bump @types/nodemailer from 7.0.4 to 7.0.5 by @dependabot[bot] in build(deps-dev): bump @types/nodemailer from 7.0.4 to 7.0.5 #87
build(deps-dev): bump @pulumi/aws from 7.15.0 to 7.16.0 by @dependabot[bot] in build(deps-dev): bump @pulumi/aws from 7.15.0 to 7.16.0 #90
build(deps): bump @aws-sdk/client-sesv2 from 3.964.0 to 3.966.0 by @dependabot[bot] in build(deps): bump @aws-sdk/client-sesv2 from 3.964.0 to 3.966.0 #86
docs: update user instructions by @Rindrics in docs: update user instructions #96
build(deps-dev): bump @types/node from 25.0.3 to 25.0.5 by @dependabot[bot] in build(deps-dev): bump @types/node from 25.0.3 to 25.0.5 #88
build(deps-dev): bump @biomejs/biome from 2.3.11 to 2.3.15 by @dependabot[bot] in build(deps-dev): bump @biomejs/biome from 2.3.11 to 2.3.15 #99
build(deps): bump mailparser from 3.9.1 to 3.9.3 by @dependabot[bot] in build(deps): bump mailparser from 3.9.1 to 3.9.3 #102
build(deps-dev): bump dotenv from 17.2.3 to 17.3.1 by @dependabot[bot] in build(deps-dev): bump dotenv from 17.2.3 to 17.3.1 #101

Full Changelog: v0.1.5...tagpr-from-v0.1.5

Summary by CodeRabbit

Chores
- Version 0.1.6 released with package version update
Documentation
- Updated changelog with v0.1.6 release notes documenting build improvements, new features, CI/CD updates, documentation changes, and corrections

coderabbitai · 2026-02-09T19:25:28Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 63077d6 and c8d1031.

📒 Files selected for processing (2)

CHANGELOG.md
packages/core/package.json

🚧 Files skipped from review as they are similar to previous changes (2)

CHANGELOG.md
packages/core/package.json

📝 Walkthrough

Walkthrough

Adds a new v0.1.6 section to CHANGELOG.md with multiple entries (build, chore, feat, revert, ci, docs) and increments packages/core/package.json version from 0.1.5 to 0.1.6.

Changes

Cohort / File(s)	Summary
Release metadata `CHANGELOG.md`, `packages/core/package.json`	Inserted a new `v0.1.6` changelog block with multiple entries (build, chore, feat, revert, ci, docs). Bumped `packages/core` version from `0.1.5` → `0.1.6`. No changes to public API or other files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Release for v0.1.3 #58 — Adds a changelog entry and bumps packages/core version (similar release update).
Prepare for publishing to npm #48 — Modifies packages/core/package.json metadata during rename; touches same manifest.
Release for v0.1.5 #65 — Consecutive release metadata updates: changelog and package version changes.

Suggested labels

Review effort 1/5

Poem

🐰 I hopped along the changelog line,
Patted a version up to shine,
Wrote a feat, a build, a tiny revert,
Danced through docs with a joyful spurt,
Nibbled the tag — now all is fine. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Release for v0.1.6' directly and clearly describes the main purpose of the pull request, which is to prepare and release version 0.1.6 as confirmed by the PR objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch tagpr-from-v0.1.5

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

qodo-free-for-open-source-projects · 2026-02-09T19:25:31Z

Review Summary by Qodo

Release v0.1.6 with dependency updates

📦 Other

Walkthroughs

Description

• Bump version from 0.1.5 to 0.1.6
• Update CHANGELOG.md with v0.1.6 release notes
• Document dependency update for vite-tsconfig-paths

Diagram

flowchart LR
  A["v0.1.5"] -- "bump version" --> B["v0.1.6"]
  C["package.json"] -- "update version" --> B
  D["CHANGELOG.md"] -- "add release notes" --> B

File Changes

1. packages/core/package.json ⚙️ Configuration changes +1/-1

Bump package version to 0.1.6
• Update version field from 0.1.5 to 0.1.6
packages/core/package.json

2. CHANGELOG.md 📝 Documentation +3/-0

Add v0.1.6 release notes to changelog

• Add new v0.1.6 release section with date 2026-02-09
• Document vite-tsconfig-paths dependency bump from 6.0.3 to 6.0.4
• Include link to related pull request #89

CHANGELOG.md

qodo-free-for-open-source-projects · 2026-02-09T19:27:22Z

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Duplicate v0.1.5 entry 🐞 Bug ✧ Quality

Description

• CHANGELOG.md contains two separate sections labeled v0.1.5 with different dates, which makes
  release notes ambiguous and harder to trust.
• Since this PR adds v0.1.6 on top, it’s a good opportunity to consolidate the duplicated v0.1.5
  sections into a single entry to avoid confusion for users and maintainers.

Code

CHANGELOG.md[6]

## [v0.1.5](https://github.com/Rindrics/slackmail/compare/v0.1.4...v0.1.5) - 2026-01-09

Evidence

The merged changelog will include two headers for the same version (v0.1.5), indicating duplicated
release sections.

CHANGELOG.md[6-8]
CHANGELOG.md[27-31]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`CHANGELOG.md` currently contains two separate sections for the same version (`v0.1.5`) with different dates, which creates ambiguity in release notes.

### Issue Context
This PR adds `v0.1.6` on top of the existing history; the duplicate `v0.1.5` entries remain in the file and will be merged as-is.

### Fix Focus Areas
- CHANGELOG.md[6-31]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

ⓘ The new review experience is currently in Beta. Learn more

pulumi · 2026-02-10T12:42:35Z

🍹 The Update (preview) for Rindrics/slackmail/juzumaru (at 0c2157a) was successful.

✨ Neo Explanation

This is a routine code deployment that updates both the S3 and Slack Lambda functions with new build artifacts, with no risk of downtime or data loss.

Root Cause Analysis

The developer updated the source code for both Lambda functions — the S3 event handler (s3-handler.js) and the Slack notification handler (slack-handler.js). Both compiled distribution files in ./dist/ have changed, triggering a redeployment of the corresponding Lambda functions.

Dependency Chain

The updated ./dist/ build artifacts are packaged and uploaded as new Lambda deployment bundles. Both functions are updated in-place (no replacement), so all associated triggers, permissions, environment variables, and configurations remain intact.

Risk analysis

No stateful resources are being modified, replaced, or deleted. Both Lambda functions are updated in-place with zero expected downtime — AWS swaps the code atomically.

Resource Changes

    Name          Type                          Operation
~   s3-lambda     aws:lambda/function:Function  update
~   slack-lambda  aws:lambda/function:Function  update

Rindrics added the tagpr label Feb 9, 2026

Rindrics force-pushed the tagpr-from-v0.1.5 branch 2 times, most recently from 9558c06 to 12f2cca Compare February 10, 2026 12:41

Rindrics force-pushed the tagpr-from-v0.1.5 branch 7 times, most recently from 3c14bcb to 63077d6 Compare February 15, 2026 15:23

Rindrics force-pushed the tagpr-from-v0.1.5 branch from 63077d6 to 0c2157a Compare February 25, 2026 02:38

Rindrics added 2 commits February 25, 2026 11:38

[tagpr] prepare for the next release

8eb8008

[tagpr] update CHANGELOG.md

c8d1031

Rindrics force-pushed the tagpr-from-v0.1.5 branch from 0c2157a to c8d1031 Compare February 25, 2026 02:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Release for v0.1.6#94

Release for v0.1.6#94
Rindrics wants to merge 2 commits intomainfrom
tagpr-from-v0.1.5

Rindrics commented Feb 9, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Feb 9, 2026 •

edited

Loading

Reviews paused

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Poem

Uh oh!

qodo-free-for-open-source-projects bot commented Feb 9, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Feb 9, 2026

Uh oh!

pulumi bot commented Feb 10, 2026 •

edited

Loading

Root Cause Analysis

Dependency Chain

Risk analysis

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Comments

Conversation

Rindrics commented Feb 9, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What's Changed

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Poem

Uh oh!

qodo-free-for-open-source-projects bot commented Feb 9, 2026

Review Summary by Qodo

Walkthroughs

File Changes

Uh oh!

qodo-free-for-open-source-projects bot commented Feb 9, 2026

Code Review by Qodo

Uh oh!

pulumi bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✨ Neo Explanation

Root Cause Analysis

Dependency Chain

Risk analysis

Resource Changes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Rindrics commented Feb 9, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Feb 9, 2026 •

edited

Loading

pulumi bot commented Feb 10, 2026 •

edited

Loading