Skip to content

Update dependency msgpack to v1.2.1#47

Open
ivan-flamingo wants to merge 1 commit into
developfrom
renovate/msgpack-1.x
Open

Update dependency msgpack to v1.2.1#47
ivan-flamingo wants to merge 1 commit into
developfrom
renovate/msgpack-1.x

Conversation

@ivan-flamingo

@ivan-flamingo ivan-flamingo commented Jun 9, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Update Change
msgpack (changelog) minor ==1.1.0==1.2.1

Release Notes

msgpack/msgpack-python (msgpack)

v1.2.1

Compare Source

Release Date: 2026-06-19

Fix a segfault when calling Unpacker.unpack() or Unpacker.skip() after an unpacking failure.
But note that reusing the same Unpacker instance after an unpacking failure is not supported.
Please create a new Unpacker instance instead. GHSA-6v7p-g79w-8964

v1.2.0

Compare Source

Release Date: 2026-06-11

  • Support free threaded Python. #​654, #​686
  • Dropped support for Python 3.9. #​656
  • Fix missing error checks in C code. #​665, #​666, #​667, #​672
  • Fix strict_map_key option didn't work for object_pairs_hook. #​673
  • Increase DEFAULT_RECURSE_LIMIT of Unpacker to 1024. #​676
  • Fix memory leak when Unpacker returns error for invalid input. #​671
  • Fix Packer.pack_ext_type() ignored autoreset option. #​663
  • Fix Timestamp.from_datetime() returning wrong value for pre-epoch datetimes. #​662
  • Fix use-after-free in unpackb() and Unpacker.unpack() for non-contiguous input. #​677
  • Fix possible memory leak when calling Unpacker.__init__() several times. #​687

v1.1.2

Compare Source

Release Date: 2025-10-08

This release does not change source code. It updates only building
wheels:

  • Update Cython to v3.1.4
  • Update cibuildwheel to v3.2.0
  • Drop Python 3.8
  • Add Python 3.14
  • Add windows-arm

v1.1.1

Compare Source

Release Date: 2025-06-13

  • No change from 1.1.1rc1.

Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, 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 has been generated by Mend Renovate.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 339c953a-3605-4070-9298-7512b0f826a9

📥 Commits

Reviewing files that changed from the base of the PR and between 42245ca and 68e711c.

📒 Files selected for processing (1)
  • api/tacticalrmm/requirements.txt
🚧 Files skipped from review as they are similar to previous changes (1)
  • api/tacticalrmm/requirements.txt

📝 Walkthrough

Walkthrough

The PR updates the pinned msgpack dependency from version 1.1.0 to 1.2.1 in api/tacticalrmm/requirements.txt. No other dependencies change.

Changes

Dependency Update

Layer / File(s) Summary
Msgpack version pin update
api/tacticalrmm/requirements.txt
msgpack updated from 1.1.0 to 1.2.1.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit hops, a tiny cheer,
Msgpack climbs from old to new,
One-dot-two-dot-one is here,
Pip will fetch the freshest brew. 🐇✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely summarizes the main change: updating the msgpack dependency from 1.1.0 to 1.2.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/msgpack-1.x

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.

@ivan-flamingo ivan-flamingo force-pushed the renovate/msgpack-1.x branch from 39d088c to 42245ca Compare June 11, 2026 12:15
@ivan-flamingo ivan-flamingo changed the title Update dependency msgpack to v1.1.2 Update dependency msgpack to v1.2.0 Jun 11, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@api/tacticalrmm/requirements.txt`:
- Line 18: The PR description and the requirements.txt change disagree:
requirements.txt now pins msgpack==1.2.0 but the PR text says v1.1.2; update the
PR to accurately reflect the package change or adjust the requirements back to
1.1.2. Locate the dependency line "msgpack==1.2.0" in requirements.txt and
either (a) update the PR title/description and include relevant v1.2.0 release
notes or breaking changes, or (b) change the pinned version to "msgpack==1.1.2"
if that was intended, then run your dependency/build checks and update the PR
body to match.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f78d06b3-d9d9-4664-87d8-8bb5e978f801

📥 Commits

Reviewing files that changed from the base of the PR and between 39d088c and 42245ca.

📒 Files selected for processing (1)
  • api/tacticalrmm/requirements.txt

Comment thread api/tacticalrmm/requirements.txt Outdated
kombu==5.4.2
meshctrl==0.1.15
msgpack==1.1.0
msgpack==1.2.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify version discrepancy between PR description and actual change.

The PR description mentions updating to v1.1.2 (with only build/wheel updates), but the actual change updates to v1.2.0. This inconsistency should be clarified—if v1.2.0 is intended, the PR description should be updated to reflect the correct version and include any relevant v1.2.0 release notes or breaking changes.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@api/tacticalrmm/requirements.txt` at line 18, The PR description and the
requirements.txt change disagree: requirements.txt now pins msgpack==1.2.0 but
the PR text says v1.1.2; update the PR to accurately reflect the package change
or adjust the requirements back to 1.1.2. Locate the dependency line
"msgpack==1.2.0" in requirements.txt and either (a) update the PR
title/description and include relevant v1.2.0 release notes or breaking changes,
or (b) change the pinned version to "msgpack==1.1.2" if that was intended, then
run your dependency/build checks and update the PR body to match.

@ivan-flamingo ivan-flamingo force-pushed the renovate/msgpack-1.x branch from 42245ca to 68e711c Compare June 18, 2026 16:50
@ivan-flamingo ivan-flamingo changed the title Update dependency msgpack to v1.2.0 Update dependency msgpack to v1.2.1 Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants