Skip to content

fix(deps): update major (major) #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update major (major) #278

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 25, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
inversify (source) ^6.0.2 -> ^7.0.0 age confidence
pino (source) ^9.6.0 -> ^10.0.0 age confidence
sqs-consumer (source) ^11.6.0 -> ^14.0.0 age confidence
zod (source) ^3.24.2 -> ^4.0.0 age confidence
zod-openapi ^4.2.2 -> ^5.0.0 age confidence

Release Notes

inversify/monorepo (inversify)

v7.10.4

Compare Source

Patch Changes

v7.10.3

Compare Source

Patch Changes

v7.10.2

Compare Source

Patch Changes

v7.10.1

Patch Changes

v7.6.1

Compare Source

v7.6.0

Compare Source

v7.5.4

Compare Source

v7.5.3

Compare Source

v7.5.2

Compare Source

v7.5.1

Compare Source

v7.5.0

Compare Source

v7.4.0

Compare Source

v7.3.0

Compare Source

v7.2.0

Compare Source

v7.1.0

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source

pinojs/pino (pino)

v10.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v10.0.0...v10.1.0

v10.0.0

Compare Source

The only breaking change is dropping support for Node 18.

What's Changed

Full Changelog: pinojs/pino@v9.13.1...v10.0.0

v9.14.0

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.13.1...v9.14.0

v9.13.1

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.13.0...v9.13.1

v9.13.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.12.0...v9.13.0

v9.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.11.0...v9.12.0

v9.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.10.0...v9.11.0

v9.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.9.5...v9.10.0

v9.9.5

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.9.4...v9.9.5

v9.9.4

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.9.3...v9.9.4

v9.9.3

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.9.2...v9.9.3

v9.9.2

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.9.1...v9.9.2

v9.9.1

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.9.0...v9.9.1

v9.9.0

Compare Source

What's Changed

Full Changelog: pinojs/pino@v9.8.0...v9.9.0

v9.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v9.7.0...v9.8.0

bbc/sqs-consumer (sqs-consumer)

v14.1.0

Compare Source

Features
Dependency Updates
Dev Dependency Updates

v14.0.1

Compare Source

This release adds on changes to start the deprecation of void, this should have been part of the v14 release and that is why it has been considered a patch change / a bug fix. This is an attempt to reduce the likelihood of users not noticing the move to explicit returns in v14.

In a future minor release a new strictReturns flag will be added (#​604), this will not be enabled by default initially. We will gather feedback on if this setting makes sense. If it does, strictReturns will be turned on by default.

Bug Fixes
  • prepare for return void deprecation and ensure that returning void errors in typescript / console warns in the logs (#​598) (3b99825)
Chores

Updated some dependencies and adjusted Dependabot workflow

v14.0.0

Compare Source

SQS Consumer v14.0.0 Migration Guide

Overview

Version 14.0.0 introduces a breaking change to how message acknowledgment works. This change makes acknowledgment behavior more explicit and predictable, addressing user confusion about when messages are acknowledged.

What Changed

Previous Behavior (<=v13.x)
  • Messages were acknowledged automatically in certain scenarios
  • Returning void (nothing) from handlers had implicit acknowledgment behavior
  • Users were often unclear about when messages would be acknowledged
New Behavior (>=v14.0)
  • Explicit acknowledgment only: Messages are acknowledged only when explicitly returned
  • Returning void (nothing) means no acknowledgment by default
  • Clear, predictable behavior based on what your handler returns

Benefits of the New Approach

  • Clarity: Explicit acknowledgment makes code intent clear
  • Reliability: Reduce accidental acknowledgment of failed processing
  • Debugging: Easier to trace acknowledgment behavior
  • Flexibility: Fine-grained control over which messages are acknowledged

Migration Steps

handleMessage()
Step 1: Identify Your Current Handler Pattern

First, determine which pattern your current message handlers follow:

// Pattern A: Handler that processes and implicitly acknowledges
const handleMessage = async (message) => {
  await processMessage(message);
  // No explicit return - was implicitly acknowledged in v13.x
};

// Pattern B: Handler with conditional acknowledgment
const handleMessage = async (message) => {
  const success = await processMessage(message);
  if (success) {
    return message; // Only acknowledge on success
  }
  // Don't acknowledge on failure
};

// Pattern C: Error handling
const handleMessage = async (message) => {
  try {
    await processMessage(message);
  } catch (error) {
    // Message acknowledgment behavior was unclear
    throw error;
  }
};
Step 2: Update Your Handlers
For Pattern A (Implicit Acknowledgment)

Option 1: Explicit Return

const consumer = Consumer.create({
  queueUrl: 'your-queue-url',
  handleMessage: async (message) => {
    console.log('Processing:', message.Body);
    await processMessage(message);
    return message; // Explicit acknowledgment
  }
});

Option 2: Use alwaysAcknowledge

const consumer = Consumer.create({
  queueUrl: 'your-queue-url',
  alwaysAcknowledge: true, // Maintains v13.x behavior
  handleMessage: async (message) => {
    console.log('Processing:', message.Body);
    await processMessage(message);
    return undefined; // Will be acknowledged due to alwaysAcknowledge setting
  }
});
For Pattern B and C (Conditional Acknowledgment)
const consumer = Consumer.create({
  queueUrl: 'your-queue-url',
  handleMessage: async (message) => {
    try {
      await processMessage(message);
      return message; // Acknowledge on success
    } catch (error) {
      console.error('Processing failed:', error);
      return undefined; // Don't return anything - message won't be acknowledged (you could also re-throw the error here)
      // It will be retried based on your queue's redrive policy
    }
  }
});
handleMessageBatch()

This is largely similar to the above recommendations, you just need to adjust to build up an array of the messages that you want to acknowledge and then return that array.

const handleMessageBatch = async (messages) => {
  const processed = [];
  
  for (const message of messages) {
    try {
      await processMessage(message);
      processed.push(message); // Add to acknowledgment list
    } catch (error) {
      console.error('Failed to process message:', error);
      return undefined; // Don't add to processed array - won't be acknowledged (you could also re-throw the error here)
    }
  }
  
  return processed; // Only acknowledge successfully processed messages
};

Configuration Options

alwaysAcknowledge Setting

Use this setting to maintain <=v13.x behavior during migration:

const consumer = Consumer.create({
  queueUrl: 'your-queue-url',
  alwaysAcknowledge: true, // Messages acknowledged regardless of return value
  handleMessage: async (message) => {
    await processMessage(message);
    return undefined; // Will be acknowledged due to alwaysAcknowledge: true
  }
});

⚠️ Warning: alwaysAcknowledge: true should be used as a temporary migration aid. The explicit return pattern is recommended for long-term maintainability.

Features
  • breaking: do not acknowledge if void is returned (#​583) (5bfb740)
Bug Fixes
  • set specific node version for now (c4729b4)
Chores

v13.0.0

Compare Source

Potentially breaking change: This release has upgraded AWS SDK from 3.7x to 3.8x, these versions will include breaking changes.

Bug Fixes
  • set specific node version (6943e7b)
Chores

v12.0.0

Compare Source

Chores
colinhacks/zod (zod)

v4.1.13

Compare Source

v4.1.12

Compare Source

Commits:

v4.1.11

Compare Source

Commits:

v4.1.10

Compare Source

Commits:

v4.1.9

Compare Source

Commits:

v4.1.8

Compare Source

Commits:

v4.1.7

Compare Source

Commits:

v4.1.6

Compare Source

v4.1.5

Compare Source

Commits:

v4.1.4

Compare Source

Commits:

  • 3291c61 fix(v4): toJSONSchema - wrong tuple with null output when targeting openapi-3.0 (#​5156)
  • 23f41c7 test(v4): toJSONSchema - use validateOpenAPI30Schema in all relevant scenarios (#​5163)
  • 0a09fd2 Update installation instructions
  • 4ea5fec 4.1.4

v4.1.3

Compare Source

Commits:

  • 98ff675 Drop stringToBoolean
  • a410616 Fix typo
  • 0cf4589 fix(v4): toJSONSchema - add missing oneOf inside items in tuple conversion (#​5146)
  • 8bf0c16 fix(v4): toJSONSchema tuple path handling for draft-7 with metadata IDs (#​5152)
  • 5c5fa90 fix(v4): toJSONSchema - wrong record output when targeting openapi-3.0 (#​5141)
  • 87b97cc docs(codecs): update example to use payloadSchema (#​5150)
  • 309f358 fix(v4): toJSONSchema - output numbers with exclusive range correctly when targeting openapi-3.0 (#​5139)
  • 1e71ca9 docs: fix refine fn to encode works properly (#​5148)
  • a85ec3c fix(docs): correct example to use LooseDog instead of Dog (#​5136)
  • 3e98274 4.1.3

v4.1.2

Compare Source

Configuration

📅 Schedule: Branch creation - "after 9pm,before 5am" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from 0265eff to 9be90cd Compare July 9, 2025 23:36
@renovate renovate bot force-pushed the renovate/major-major branch 7 times, most recently from 9212cb7 to 3ad1249 Compare July 30, 2025 11:48
@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from a9f1a3d to b23b021 Compare August 6, 2025 02:22
@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from 9b32901 to 43005b2 Compare August 11, 2025 18:25
@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from 11fd293 to fdb34f2 Compare August 21, 2025 02:59
@renovate renovate bot force-pushed the renovate/major-major branch 8 times, most recently from 2d4ed5b to 07f29bf Compare August 27, 2025 21:56
@renovate renovate bot force-pushed the renovate/major-major branch from 07f29bf to 8a38bc2 Compare August 31, 2025 08:59
@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from 8caa4ae to 85472bf Compare September 14, 2025 21:37
@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from d54f8ce to 1bb30dc Compare September 20, 2025 21:06
@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from 69b1486 to 1efa3a7 Compare September 30, 2025 17:38
@renovate renovate bot force-pushed the renovate/major-major branch 4 times, most recently from d212306 to 7020cbc Compare October 8, 2025 16:37
@renovate renovate bot force-pushed the renovate/major-major branch 3 times, most recently from c77c611 to 3e99f7b Compare October 21, 2025 17:43
@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from db5df9a to 9ecd773 Compare November 1, 2025 00:28
@renovate renovate bot force-pushed the renovate/major-major branch from 9ecd773 to c0efd6a Compare November 10, 2025 18:05
@renovate renovate bot force-pushed the renovate/major-major branch 2 times, most recently from b50acbd to 0daf5ec Compare November 24, 2025 05:59
@renovate renovate bot force-pushed the renovate/major-major branch from 0daf5ec to 715009d Compare November 27, 2025 05:10
@renovate renovate bot force-pushed the renovate/major-major branch from 715009d to f6bbc40 Compare November 27, 2025 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant