Skip to content

Commit

Permalink
chore(release): version packages (#107)
Browse files Browse the repository at this point in the history
closes #105

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
  • Loading branch information
github-actions[bot] and github-actions[bot] authored Feb 9, 2025
1 parent b0445bb commit 60ab933
Show file tree
Hide file tree
Showing 99 changed files with 2,799 additions and 200 deletions.
52 changes: 0 additions & 52 deletions .changeset/shy-needles-rhyme.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/tough-planets-talk.md

This file was deleted.

95 changes: 0 additions & 95 deletions .changeset/violet-glasses-accept.md

This file was deleted.

63 changes: 63 additions & 0 deletions packages/client-account/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,68 @@
# @effect-aws/client-account

## 1.9.0

### Minor Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - ## Refactored service configuration and layer management

Since this version the effectful logger is not added into native AWS client constructor. Providing logger by default causes risk of logging sensitive information. The logger should be added explicitly by the choice of a user. It can be done by using extended `logger` option:

```ts
import { DynamoDB } from "@effect-aws/client-dynamodb";

// using default logger
DynamoDB.layer({ logger: true });

// or using custom logger (the same as default)
DynamoDB.layer({
logger: {
trace: Effect.logTrace,
debug: Effect.logDebug,
info: Effect.logInfo,
warn: Effect.logWarning,
error: Effect.logError,
},
});

// and you could remap logger methods as you want
DynamoDB.layer({
logger: {
debug: Effect.logDebug,
info: Effect.logDebug,
warn: Effect.logWarning,
error: Effect.logError,
},
});
```

Additionally to that, the whole service configuration was refactored in better way, now it is not a strict layer dependency, but the global value which defaults to empty object. The global value can be configured by using the effect higher order function or the layer setter.

```ts
import { DynamoDBServiceConfig } from "@effect-aws/client-dynamodb";

// using effect higher order function
DynamoDBServiceConfig.withDynamoDBServiceConfig({ logger: true });

// or using layer setter
Layer.provide(
DynamoDBServiceConfig.setDynamoDBServiceConfig({ logger: true }),
);
```

### Breaking changes

This release is not a breaking change if you just use service methods and service layer, which in most cases should be the case.

If you had to use custom configuration, you should update your code to use new configuration methods.

### Patch Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - drop support for effect version lower than 3.0.4

- Updated dependencies [[`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f), [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f)]:
- @effect-aws/commons@0.1.0

## 1.3.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/client-account/package.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

63 changes: 63 additions & 0 deletions packages/client-api-gateway-management-api/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,68 @@
# @effect-aws/client-api-gateway-management-api

## 1.9.0

### Minor Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - ## Refactored service configuration and layer management

Since this version the effectful logger is not added into native AWS client constructor. Providing logger by default causes risk of logging sensitive information. The logger should be added explicitly by the choice of a user. It can be done by using extended `logger` option:

```ts
import { DynamoDB } from "@effect-aws/client-dynamodb";

// using default logger
DynamoDB.layer({ logger: true });

// or using custom logger (the same as default)
DynamoDB.layer({
logger: {
trace: Effect.logTrace,
debug: Effect.logDebug,
info: Effect.logInfo,
warn: Effect.logWarning,
error: Effect.logError,
},
});

// and you could remap logger methods as you want
DynamoDB.layer({
logger: {
debug: Effect.logDebug,
info: Effect.logDebug,
warn: Effect.logWarning,
error: Effect.logError,
},
});
```

Additionally to that, the whole service configuration was refactored in better way, now it is not a strict layer dependency, but the global value which defaults to empty object. The global value can be configured by using the effect higher order function or the layer setter.

```ts
import { DynamoDBServiceConfig } from "@effect-aws/client-dynamodb";

// using effect higher order function
DynamoDBServiceConfig.withDynamoDBServiceConfig({ logger: true });

// or using layer setter
Layer.provide(
DynamoDBServiceConfig.setDynamoDBServiceConfig({ logger: true }),
);
```

### Breaking changes

This release is not a breaking change if you just use service methods and service layer, which in most cases should be the case.

If you had to use custom configuration, you should update your code to use new configuration methods.

### Patch Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - drop support for effect version lower than 3.0.4

- Updated dependencies [[`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f), [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f)]:
- @effect-aws/commons@0.1.0

## 1.6.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/client-api-gateway-management-api/package.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

63 changes: 63 additions & 0 deletions packages/client-auto-scaling/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,68 @@
# @effect-aws/client-auto-scaling

## 1.9.0

### Minor Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - ## Refactored service configuration and layer management

Since this version the effectful logger is not added into native AWS client constructor. Providing logger by default causes risk of logging sensitive information. The logger should be added explicitly by the choice of a user. It can be done by using extended `logger` option:

```ts
import { DynamoDB } from "@effect-aws/client-dynamodb";

// using default logger
DynamoDB.layer({ logger: true });

// or using custom logger (the same as default)
DynamoDB.layer({
logger: {
trace: Effect.logTrace,
debug: Effect.logDebug,
info: Effect.logInfo,
warn: Effect.logWarning,
error: Effect.logError,
},
});

// and you could remap logger methods as you want
DynamoDB.layer({
logger: {
debug: Effect.logDebug,
info: Effect.logDebug,
warn: Effect.logWarning,
error: Effect.logError,
},
});
```

Additionally to that, the whole service configuration was refactored in better way, now it is not a strict layer dependency, but the global value which defaults to empty object. The global value can be configured by using the effect higher order function or the layer setter.

```ts
import { DynamoDBServiceConfig } from "@effect-aws/client-dynamodb";

// using effect higher order function
DynamoDBServiceConfig.withDynamoDBServiceConfig({ logger: true });

// or using layer setter
Layer.provide(
DynamoDBServiceConfig.setDynamoDBServiceConfig({ logger: true }),
);
```

### Breaking changes

This release is not a breaking change if you just use service methods and service layer, which in most cases should be the case.

If you had to use custom configuration, you should update your code to use new configuration methods.

### Patch Changes

- [#106](https://github.com/floydspace/effect-aws/pull/106) [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f) Thanks [@floydspace](https://github.com/floydspace)! - drop support for effect version lower than 3.0.4

- Updated dependencies [[`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f), [`e07e3c0`](https://github.com/floydspace/effect-aws/commit/e07e3c0d8e9e03650e1fd443b1c5a6bdc14baa3f)]:
- @effect-aws/commons@0.1.0

## 1.1.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/client-auto-scaling/package.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading

0 comments on commit 60ab933

Please sign in to comment.