fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) by renovate[bot] · Pull Request #131 · devopsfactory-io/neptune

renovate · 2026-04-13T02:32:26Z

This PR contains the following updates:

Package	Type	Update	Change	Pending
github.com/aws/aws-sdk-go-v2	require	minor	`v1.41.5` → `v1.47.1`	`v1.47.2`
github.com/aws/aws-sdk-go-v2/config	require	minor	`v1.32.14` → `v1.33.6`	`v1.33.8` (+1)
github.com/aws/aws-sdk-go-v2/service/s3	require	minor	`v1.98.0` → `v1.114.0`	`v1.114.2` (+1)
github.com/aws/aws-sdk-go-v2/service/secretsmanager	require	minor	`v1.41.5` → `v1.50.1`	`v1.50.3` (+1)

Release Notes

aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)

`v1.47.1`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.49.0
- Feature: Batch evaluation now supports evaluating specific traces within a session. Each session can specify up to 100 trace IDs to evaluate.
github.com/aws/aws-sdk-go-v2/service/connect: v1.200.0
- Feature: Made the replicaAlias attribute optional in the ReplicateInstance API to support Global routing for Amazon Connect Global Resiliency (ACGR) instances. This change maintains backward compatibility. When onboarding to ACGR without Global routing, you must specify a custom replicaAlias in your API call
github.com/aws/aws-sdk-go-v2/service/ec2: v1.334.0
- Feature: Adding support for "Tunnel" VPC Endpoint
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.93.0
- Feature: This change surfaces AI Protection resources on existing public IAM attack sequences. Customers will now see which model was accessed and whether a guardrail intervened as part of the credential-compromise sequence.
github.com/aws/aws-sdk-go-v2/service/iotwireless: v1.65.0
- Feature: Adds Multi-frame GNSS support to the AWS IoT Core Device Location GetPositionEstimate API. The new GnssMultiFrame measurement type improves location accuracy by combining multiple GNSS signal captures (2, 4, 8, 16, or 32) from the same device to estimate its position.
github.com/aws/aws-sdk-go-v2/service/notifications: v1.17.0
- Feature: Added support for attachments on managed notification events. Added support to access and subscribe sensitive managed notification events.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.74.0
- Feature: Added support to query the tenant name for BatchGetMetricData and CreateExportJob APIs to filter metrics and messages at the tenant level.
github.com/aws/aws-sdk-go-v2/service/sns: v1.47.1
- Documentation: SNS API reference documentation update
github.com/aws/aws-sdk-go-v2/service/socialmessaging: v1.21.0
- Feature: Add support for WhatsApp Calling APIs.
github.com/aws/aws-sdk-go-v2/service/vpclattice: v1.33.0
- Feature: Adding support for CIDR Resource Configuration

`v1.47.0`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2/service/aiops: v1.17.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/backup: v1.68.0
- Feature: Enable schema-based (de)serialization for this service.
- Bug Fix: BREAKING CHANGE: The ValidationWindowHours field on RestoreTestingSelectionForCreate and RestoreTestingSelectionForUpdate has been changed from int32 to *int32. Before this change, the field was incorrectly marked as having a default value of 0 by the service, which made it functionally impossible for users to set it to 0 in an UpdateRestoreTestingSelection call.
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.74.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.54.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eks: v1.103.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/freetier: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/glue: v1.168.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.98.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/health: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/healthlake: v1.52.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.48.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.18.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.111.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdacore: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdamicrovms: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdaweb: v1.1.0
- Feature: Removes operations that are not yet generally available from the Lambda Web.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mturk: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mwaaserverless: v1.12.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.75.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/odb: v1.25.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.84.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralaccount: v1.16.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralbenefits: v1.11.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pinpointemail: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.135.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakermetrics: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.78.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.46.0`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2/service/aiops: v1.16.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.26.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.32.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.32.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/backup: v1.67.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudwatch: v1.73.0
- Feature: This release adds Create, Get, Update, and DeleteResourceMetricsConfiguration to enable detailed metric collection for an AWS resource, and adds UpdateOTelEnrichment plus include and exclude filters on StartOTelEnrichment so you can choose which metric namespaces CloudWatch enriches.
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.73.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datazone: v1.76.0
- Feature: Amazon DataZone now supports the TOOLING blueprint category on CreateEnvironmentBlueprint, UpdateEnvironmentBlueprint, GetEnvironmentBlueprint, and ListEnvironmentBlueprints, for custom tooling blueprints. CreateConnection now accepts roleArn in iamProperties.
github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.53.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eks: v1.101.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/elasticache: v1.62.0
- Feature: Added tagging support for ElastiCache Global DataStore.
github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.55.0
- Feature: Adds a ManagedBy field to the DescribeEventBus and ListEventBuses responses, identifying the AWS service that created an event bus on your behalf.
github.com/aws/aws-sdk-go-v2/service/eventbridgev2: v1.0.0
- Release: New AWS service client module
- Feature: Introducing Amazon EventBridge enhanced Custom event bus, a new shareable event bus for organizational-scale event-driven applications feature ordered delivery, deduplication, open event formats, and cross-account bus sharing.
github.com/aws/aws-sdk-go-v2/service/evs: v1.22.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/freetier: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/glue: v1.163.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.95.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/health: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/healthlake: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.21.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iot: v1.84.1
- Documentation: Fixed ListV2LoggingLevels and DeleteV2LoggingLevel documentation to include all supported target-types
github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.35.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.17.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.110.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdacore: v1.9.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdamicrovms: v1.9.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplacediscovery: v1.11.0
- Feature: AWS Marketplace Discovery API now supports localized responses and SigV4a request signing. It returns new fulfillment details, including AMI architecture, EBS volume and security group information, SaaS quick-launch status, and SageMaker input and output MIME types.
github.com/aws/aws-sdk-go-v2/service/mturk: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mwaaserverless: v1.11.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.74.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/odb: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.82.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralaccount: v1.15.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralbenefits: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pinpointemail: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.133.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/redshiftdata: v1.49.0
- Feature: Updates to the ListDatabases and WorkgroupName validation
github.com/aws/aws-sdk-go-v2/service/route53resolver: v1.54.1
- Documentation: Documentation updates for Route 53 Resolver. Clarifies which Outpost Resolver operations apply to first-generation AWS Outposts and that Resolver is managed automatically on second-generation Outposts. Adds Local Network Interface subnet compatibility notes for Resolver endpoints.
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakermetrics: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/securityagent: v1.18.0
- Feature: Added support for Confluence export, enabling customers to publish security findings to Confluence pages.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.76.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.45.1`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.45.1
- Bug Fix: Fix internal timeout gate to not depend on env opt-in.
github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager: v0.4.1
- Bug Fix: Fix DownloadObject bug so parts can be read to correct offset regardless of parts sizes change
- Bug Fix: Fix GetObject bug so object parts can be read to correct offset regardless of parts sizes change

`v1.45.0`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2/service/aiops: v1.17.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/backup: v1.68.0
- Feature: Enable schema-based (de)serialization for this service.
- Bug Fix: BREAKING CHANGE: The ValidationWindowHours field on RestoreTestingSelectionForCreate and RestoreTestingSelectionForUpdate has been changed from int32 to *int32. Before this change, the field was incorrectly marked as having a default value of 0 by the service, which made it functionally impossible for users to set it to 0 in an UpdateRestoreTestingSelection call.
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.74.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.54.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eks: v1.103.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/freetier: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/glue: v1.168.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.98.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/health: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/healthlake: v1.52.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.48.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.18.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.111.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdacore: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdamicrovms: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdaweb: v1.1.0
- Feature: Removes operations that are not yet generally available from the Lambda Web.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mturk: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mwaaserverless: v1.12.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.75.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/odb: v1.25.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.84.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralaccount: v1.16.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralbenefits: v1.11.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pinpointemail: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.135.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakermetrics: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.78.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.44.0`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2/service/aiops: v1.17.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/backup: v1.68.0
- Feature: Enable schema-based (de)serialization for this service.
- Bug Fix: BREAKING CHANGE: The ValidationWindowHours field on RestoreTestingSelectionForCreate and RestoreTestingSelectionForUpdate has been changed from int32 to *int32. Before this change, the field was incorrectly marked as having a default value of 0 by the service, which made it functionally impossible for users to set it to 0 in an UpdateRestoreTestingSelection call.
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.74.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.54.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eks: v1.103.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/freetier: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/glue: v1.168.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.98.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/health: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/healthlake: v1.52.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.48.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.18.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.111.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdacore: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdamicrovms: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdaweb: v1.1.0
- Feature: Removes operations that are not yet generally available from the Lambda Web.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mturk: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mwaaserverless: v1.12.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.75.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/odb: v1.25.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.84.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralaccount: v1.16.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralbenefits: v1.11.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pinpointemail: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.135.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakermetrics: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.78.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.43.8`

Compare Source

General Highlights

Dependency Update: Update to smithy-go v1.27.10.
Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.43.8
- Bug Fix: Make X-Amz-Checksum-Mode appear on query parameters on presigned URLs
github.com/aws/aws-sdk-go-v2/service/account: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/acmpca: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.73.0
- Feature: Adds support for Distribution Segments in mixed instances policies, providing ordered prioritization across On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and On-Demand capacity.
github.com/aws/aws-sdk-go-v2/service/billingconductor: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudcontrol: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudhsmv2: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudwatchevents: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codebuild: v1.73.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codegurureviewer: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codepipeline: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dataexchange: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/deadline: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/detective: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devopsagent: v1.11.0
- Feature: Adds the UpdateApprovalAction API for resolving agent action approvals in AWS DevOps Agent agent spaces.
github.com/aws/aws-sdk-go-v2/service/directoryservice: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/drs: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2: v1.323.0
- Feature: Fleet feature to support Capacity Reservation Resource Groups with Amazon EC2 Capacity Blocks and interruptible Capacity Reservations
github.com/aws/aws-sdk-go-v2/service/eks: v1.93.0
- Feature: This feature would give customers the ability to tune TerminatedPodGcThreshold configuration in an Amazon EKS cluster.
github.com/aws/aws-sdk-go-v2/service/emrcontainers: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.14.0
- Feature: EVS now supports i7i.metal-48xl EC2 bare metal instance type, delivering high random IOPS performance with real-time latency, ideal for IO intensive and latency-sensitive workloads such as transactional databases, real-time analytics, and AI ML pre-processing.
github.com/aws/aws-sdk-go-v2/service/frauddetector: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/fsx: v1.69.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/globalaccelerator: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iamtoolbox: v1.0.0
- Release: New AWS service client module
- Feature: AWS Identity and Access Management (IAM) announces access troubleshooter, helping you debug access denied errors faster. Supported error messages now include an identifier you can use to retrieve detailed evaluations of the policies considered and their results. Preview in US East (N. Virginia).
github.com/aws/aws-sdk-go-v2/service/inspector: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iot: v1.78.0
- Feature: As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT InfluxDB Action. The IoT InfluxDB action lets customers send messages from IoT sensors and applications to InfluxDB.
github.com/aws/aws-sdk-go-v2/service/iotsecuretunneling: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iottwinmaker: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ivs: v1.56.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ivsrealtime: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
`github.com/aws/aws-sdk-go-v2/service

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM (* 0-3 * * *)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

github-actions · 2026-04-13T02:32:43Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 65bba25
Repo: devopsfactory-io/neptune

github-actions · 2026-04-13T02:34:56Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-13T02:35:01Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=1672035333654671910]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=1793228703302593031]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-14T05:47:24Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b04c298
Repo: devopsfactory-io/neptune

github-actions · 2026-04-14T05:48:14Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-14T05:48:18Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=192325180287796311]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=7533449980934697436]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-21T23:52:55Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b85da25
Repo: devopsfactory-io/neptune

github-actions · 2026-04-21T23:55:06Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-21T23:55:10Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=3776322936138890563]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=1181713196680866156]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-22T21:35:52Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 3d5b53c
Repo: devopsfactory-io/neptune

renovate · 2026-04-22T21:35:54Z

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

15 additional dependencies were updated

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package	Change
`github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream`	`v1.7.8` -> `v1.7.20`
`github.com/aws/aws-sdk-go-v2/credentials`	`v1.19.14` -> `v1.20.6`
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`	`v1.18.21` -> `v1.20.1`
`github.com/aws/aws-sdk-go-v2/internal/configsources`	`v1.4.21` -> `v1.5.4`
`github.com/aws/aws-sdk-go-v2/internal/endpoints/v2`	`v2.7.21` -> `v2.8.4`
`github.com/aws/aws-sdk-go-v2/internal/v4a`	`v1.4.22` -> `v1.5.4`
`github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding`	`v1.13.7` -> `v1.13.19`
`github.com/aws/aws-sdk-go-v2/service/internal/checksum`	`v1.9.13` -> `v1.11.5`
`github.com/aws/aws-sdk-go-v2/service/internal/presigned-url`	`v1.13.21` -> `v1.14.4`
`github.com/aws/aws-sdk-go-v2/service/internal/s3shared`	`v1.19.21` -> `v1.20.4`
`github.com/aws/aws-sdk-go-v2/service/signin`	`v1.0.9` -> `v1.10.1`
`github.com/aws/aws-sdk-go-v2/service/sso`	`v1.30.15` -> `v1.38.1`
`github.com/aws/aws-sdk-go-v2/service/ssooidc`	`v1.35.19` -> `v1.43.1`
`github.com/aws/aws-sdk-go-v2/service/sts`	`v1.41.10` -> `v1.51.1`
`github.com/aws/smithy-go`	`v1.24.2` -> `v1.28.1`

File name: lambda/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

11 additional dependencies were updated

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package	Change
`github.com/aws/aws-sdk-go-v2/credentials`	`v1.19.14` -> `v1.20.6`
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`	`v1.18.21` -> `v1.20.1`
`github.com/aws/aws-sdk-go-v2/internal/configsources`	`v1.4.21` -> `v1.5.4`
`github.com/aws/aws-sdk-go-v2/internal/endpoints/v2`	`v2.7.21` -> `v2.8.4`
`github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding`	`v1.13.7` -> `v1.13.19`
`github.com/aws/aws-sdk-go-v2/service/internal/presigned-url`	`v1.13.21` -> `v1.14.4`
`github.com/aws/aws-sdk-go-v2/service/signin`	`v1.0.9` -> `v1.10.1`
`github.com/aws/aws-sdk-go-v2/service/sso`	`v1.30.15` -> `v1.38.1`
`github.com/aws/aws-sdk-go-v2/service/ssooidc`	`v1.35.19` -> `v1.43.1`
`github.com/aws/aws-sdk-go-v2/service/sts`	`v1.41.10` -> `v1.51.1`
`github.com/aws/smithy-go`	`v1.24.2` -> `v1.28.1`

github-actions · 2026-04-22T21:38:04Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-22T21:38:08Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
null_resource.stack_a: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creation complete after 0s [id=3196650288103566860]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=7428081722819201608]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-23T05:05:06Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: c62a881
Repo: devopsfactory-io/neptune

github-actions · 2026-04-23T05:07:29Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-23T05:07:34Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
null_resource.stack_a: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creation complete after 0s [id=3507466482357218995]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=8765085218958696063]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-23T09:09:12Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 6825aa6
Repo: devopsfactory-io/neptune

github-actions · 2026-09-03T11:35:27Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-09-03T11:35:34Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=6383120596850030493]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] local_file.out: Creating...
null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=5922254049236904687]
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-09-06T00:57:51Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 0465f49
Repo: devopsfactory-io/neptune

github-actions · 2026-09-06T01:00:07Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-09-06T01:00:12Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
local_file.out: Creating...
null_resource.stack_a: Creation complete after 0s [id=1729325202596409303]
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
null_resource.stack_b: Creation complete after 0s [id=3527274522693145026]
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-09-09T21:49:08Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 9ed00e9
Repo: devopsfactory-io/neptune

coderabbitai · 2026-09-09T21:49:09Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 5071b03b-3d13-4049-8d9c-38e80af899bf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}

github-actions · 2026-09-09T21:51:34Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-09-09T21:51:40Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=4663400443007980862]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] local_file.out: Creating...
null_resource.stack_b: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=4986777761883698102]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-09-13T21:33:31Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 53f94ba
Repo: devopsfactory-io/neptune

github-actions · 2026-09-14T18:52:50Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b7aad60
Repo: devopsfactory-io/neptune

github-actions · 2026-09-16T19:07:07Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 72b9e69
Repo: devopsfactory-io/neptune

github-actions · 2026-09-19T21:56:08Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 607f070
Repo: devopsfactory-io/neptune

github-actions · 2026-09-20T22:59:21Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 41d059f
Repo: devopsfactory-io/neptune

github-actions · 2026-09-26T22:57:43Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 64fc0ad
Repo: devopsfactory-io/neptune

github-actions · 2026-09-28T21:26:29Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 46ee89c
Repo: devopsfactory-io/neptune

github-actions · 2026-09-29T18:52:15Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: ef5c227
Repo: devopsfactory-io/neptune

renovate Bot added the dependencies label Apr 13, 2026

github-actions Bot added the neptune label Apr 13, 2026

neptune-ci-tests Bot mentioned this pull request Apr 13, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#91

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from 65bba25 to b04c298 Compare April 14, 2026 05:47

neptune-ci-tests Bot mentioned this pull request Apr 14, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#94

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from b04c298 to b85da25 Compare April 21, 2026 23:52

renovate Bot changed the title ~~fix(deps): update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.99.0 in go.mod (main)~~ fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) Apr 21, 2026

neptune-ci-tests Bot mentioned this pull request Apr 21, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#102

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from b85da25 to 3d5b53c Compare April 22, 2026 21:35

neptune-ci-tests Bot mentioned this pull request Apr 22, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#104

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from 3d5b53c to c62a881 Compare April 23, 2026 05:04

neptune-ci-tests Bot mentioned this pull request Apr 23, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#105

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from c62a881 to 6825aa6 Compare April 23, 2026 09:09

neptune-ci-tests Bot mentioned this pull request Sep 3, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#274

Closed

neptune-ci-tests Bot mentioned this pull request Sep 6, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#275

Closed

neptune-ci-tests Bot mentioned this pull request Sep 9, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#276

Closed

neptune-ci-tests Bot mentioned this pull request Sep 13, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#277

Closed

neptune-ci-tests Bot mentioned this pull request Sep 14, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#278

Closed

neptune-ci-tests Bot mentioned this pull request Sep 16, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#279

Closed

neptune-ci-tests Bot mentioned this pull request Sep 19, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#280

Closed

neptune-ci-tests Bot mentioned this pull request Sep 20, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#281

Closed

neptune-ci-tests Bot mentioned this pull request Sep 26, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#302

Closed

neptune-ci-tests Bot mentioned this pull request Sep 28, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#303

Closed

neptune-ci-tests Bot mentioned this pull request Sep 29, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#304

Closed

fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod

81ced1d

neptune-ci-tests Bot mentioned this pull request Oct 5, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#305

Closed

Conversation

renovate Bot commented Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v1.47.1

Module Highlights

v1.47.0

General Highlights

Module Highlights

v1.46.0

General Highlights

Module Highlights

v1.45.1

General Highlights

Module Highlights

v1.45.0

General Highlights

Module Highlights

v1.44.0

General Highlights

Module Highlights

v1.43.8

General Highlights

Module Highlights

Configuration

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

github-actions Bot commented Apr 13, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 13, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 14, 2026

Uh oh!

github-actions Bot commented Apr 14, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 14, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 21, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 22, 2026

Uh oh!

renovate Bot commented Apr 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ℹ️ Artifact update notice

File name: go.mod

File name: lambda/go.mod

Uh oh!

github-actions Bot commented Apr 22, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 22, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 23, 2026

Uh oh!

github-actions Bot commented Apr 23, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 23, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 23, 2026

Uh oh!

github-actions Bot commented Sep 3, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Sep 3, 2026

🌊 Neptune Apply Results

Uh oh!

renovate Bot commented Apr 13, 2026 •

edited

Loading

`v1.47.1`

`v1.47.0`

`v1.46.0`

`v1.45.1`

`v1.45.0`

`v1.44.0`

`v1.43.8`

renovate Bot commented Apr 22, 2026 •

edited

Loading

coderabbitai Bot commented Sep 9, 2026 •

edited

Loading