Add option to skip signature verification (#821)

## Changes

- Allow skipping signature verification for webhooks

## Motivation

The signature returned with webhooks is calculated using a single
channel secret. If the bot owner changes their channel secret, the
signature for webhooks starts being calculated using the new channel
secret. To avoid signature verification failures, the bot owner must
update the channel secret on their server, which is used for signature
verification. However, if there is a timing mismatch in the update—and
such a mismatch is almost unavoidable—verification will fail during that
period.

In such cases, having an option to skip signature verification for
webhooks would be a convenient way to avoid these issues.

## Related PRs

- line-bot-sdk-java: line/line-bot-sdk-java#1635
- line-bot-sdk-go: line/line-bot-sdk-go#595

Add new AudienceGroupType POP_AD_IMP to Audience Group API (#842)

line/line-openapi#113

# Add `POP_AD_IMP` to **AudienceGroupType** Enum

We have supported for the new audience‑group type **`POP_AD_IMP`**
(POP ad impression audience) to the OpenAPI schema.

## Changes Made

* **Updated `AudienceGroupType` enumeration**

  * **New value**: `POP_AD_IMP`
* **Description**: Audience groups generated from impressions of *LINE
Beacon Network* (POP) ads.
  * **Region**: **Taiwan‑only** at launch

## Purpose

This update enables correct identification and handling of audience
groups built from POP ad impressions, a feature that will be released
for the Taiwan market.

## Documents and Reference

- [Managing
Audience](https://developers.line.biz/en/reference/messaging-api/#manage-audience-group)

For more information, please refer to the links provided above.

Co-authored-by: github-actions <[email protected]>

Bye line things (#840)

line/line-openapi#112

It has been already gone.
Therefore this change cleans up definition of `ThingsEvent` as one of
webhook event.

Co-authored-by: github-actions <[email protected]>

chore(deps): update actions/download-artifact action to v5 (#834)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
|
[actions/download-artifact](https://github.com/actions/download-artifact)
| action | major | `v4.3.0` -> `v5.0.0` |

---

### Release Notes

<details>
<summary>actions/download-artifact (actions/download-artifact)</summary>

###
[`v5.0.0`](https://github.com/actions/download-artifact/releases/tag/v5.0.0)

[Compare
Source](https://github.com/actions/download-artifact/compare/v4.3.0...v5.0.0)

#### What's Changed

- Update README.md by
[@&#8203;nebuk89](https://github.com/nebuk89) in
[https://github.com/actions/download-artifact/pull/407](https://github.com/actions/download-artifact/pull/407)
- BREAKING fix: inconsistent path behavior for single artifact downloads
by ID by [@&#8203;GrantBirki](https://github.com/GrantBirki) in
[https://github.com/actions/download-artifact/pull/416](https://github.com/actions/download-artifact/pull/416)

#### v5.0.0

##### 🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact
downloads by ID. **If you're downloading single artifacts by ID, the
output path may change.**

##### What Changed

Previously, **single artifact downloads** behaved differently depending
on how you specified the artifact:

- **By name**: `name: my-artifact` → extracted to `path/` (direct)
- **By ID**: `artifact-ids: 12345` → extracted to `path/my-artifact/`
(nested)

Now both methods are consistent:

- **By name**: `name: my-artifact` → extracted to `path/` (unchanged)
- **By ID**: `artifact-ids: 12345` → extracted to `path/` (fixed - now
direct)

##### Migration Guide

##### ✅ No Action Needed If:

- You download artifacts by **name**
- You download **multiple** artifacts by ID
- You already use `merge-multiple: true` as a workaround

##### ⚠️ Action Required If:

You download **single artifacts by ID** and your workflows expect the
nested directory structure.

**Before v5 (nested structure):**

```yaml
- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

### Files were in: dist/my-artifact/
```

> Where `my-artifact` is the name of the artifact you previously
uploaded

**To maintain old behavior (if needed):**

```yaml
- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path
```

#### New Contributors

- [@&#8203;nebuk89](https://github.com/nebuk89) made their
first contribution in
[https://github.com/actions/download-artifact/pull/407](https://github.com/actions/download-artifact/pull/407)

**Full Changelog**:
actions/download-artifact@v4...v5.0.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/line/line-bot-sdk-python).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS41MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNTEuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJkZXBlbmRlbmN5IHVwZ3JhZGUiXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Fix type of expireTimestamp (#802)

line/line-openapi#106

Type for `CreateAudienceGroupResponse#expireTimestamp` is not float or
double, but integer actually. This change fixes type.

Co-authored-by: github-actions <[email protected]>

Add includesOwnedAudienceGroups Parameter to Audience API (#800)

line/line-openapi#105

# Enhancement to Shared Audiences API

This PR introduces a new query parameter `includesOwnedAudienceGroups`
to the `/v2/bot/audienceGroup/shared/list` endpoint in the Business
Manager API. This enhancement allows users to specify whether to include
audience groups owned by the user in the response.

## Changes Made
- Added the `includesOwnedAudienceGroups` parameter to the API endpoint.
  - **Type**: Boolean
  - **Default**: false
  - **Description**: 
- `true`: Include audience groups owned by the LINE Official Account
Manager.
- `false`: Respond only with audience groups shared by Business Manager.
- Removed the `/v2/bot/audienceGroup/{audienceGroupId}/activate` and
`/v2/bot/audienceGroup/authorityLevel` endpoints.

## Purpose
This update provides more flexibility in retrieving audience groups by
allowing users to filter based on ownership. It is especially useful for
users who manage both shared and owned audience groups. The removal of
certain endpoints is part of a cleanup effort to streamline the API.

Please review the changes and let me know if there are any questions or
further modifications needed.

## Documents and Reference
- [Get List of Shared
Audiences](https://developers.line.biz/en/reference/messaging-api/#get-shared-audience-list)
- [Removed
Endpoints](https://developers.line.biz/en/news/2025/03/26/cross-targeting-closing/)

For more information, please refer to the links provided above.

Co-authored-by: github-actions <[email protected]>

Migrate renovate config (#782)

Renovate's auto migrator removes comments and disrupts the format as it
said.
This change keeps the original file as much as possible.

Close #777

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Modify http status code as response for manage-audience (#766)

line/line-openapi#87

This change modifies the HTTP status code for the following audience
group-related endpoints, as they were incorrect.
Some http status codes are wrong. They should be 202, not 200.
1. `POST /v2/bot/audienceGroup/upload` (`createAudienceGroup`)
2. `PUT /v2/bot/audienceGroup/upload` (`addAudienceToAudienceGroup`)
3. `POST /v2/bot/audienceGroup/upload/byFile`
(`createAudienceForUploadingUserIds`)
4. `POST /v2/bot/audienceGroup/click` (`createClickBasedAudienceGroup`)
5. `POST /v2/bot/audienceGroup/imp` (`createImpBasedAudienceGroup`)


You can also check if this change is correct by reading
https://developers.line.biz/en/reference/messaging-api/#manage-audience-group.

NOTE: This change is not a modification of the messaging API itself. It
is simply a correction of an error in the YAML description.

Co-authored-by: github-actions <[email protected]>

Publish library to pypi with OIDC (#763)

[GitHub supports deployments using OIDC as of
2023](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect).
PyPI has also released functionality to integrate with this. As a
result, it should be possible to publish without a personal access
token.

I have already registered this repository, workflow, and environment
with PyPI.
- https://pypi.org/manage/project/line-bot-sdk/settings/publishing/


### reference
-
https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-pypi
-
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
- https://docs.pypi.org/trusted-publishers/

Support new Membership API and Webhook (#758)

line/line-openapi#86

# Support new Membership API and Webhook

We have implemented and supported new API and Webhook about Membership.

## API to get a list of users who joined the membership

You can obtain a list of user IDs for users who have joined the
membership of your LINE Official Account by calling
`client.getJoinedMembershipUsers(...)`.

Documents:
https://developers.line.biz/en/reference/messaging-api/#get-membership-user-ids

## Membership Webhook 

We have introduced new Webhook events `MembershipEvent` that indicates
that a user has joined, left or renewed a membership of your LINE
Official Account.

Documents:
https://developers.line.biz/en/reference/messaging-api/#membership-event

## For more details
 
For more details, check out the announcement:
https://developers.line.biz/en/news/2025/02/13/membership-api/

Co-authored-by: github-actions <[email protected]>