You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [3.0.9] - 2025-03-03
9
+
10
+
### Security
11
+
12
+
- Updated python and npm dependencies
13
+
8
14
## [3.0.8] - 2024-11-25
9
15
10
16
### Security
@@ -47,11 +53,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
47
53
48
54
- Remove Android (AAID) and iOS (IDFA) options for Mobile Ad Id (MAID) because MAID now supersedes AAID and IDFA.
49
55
50
-
### Fixed
56
+
### Fixed
51
57
52
-
- Avoid dropping Country Code when LiveRamp, Experian, or Mobile Ad IDs are used for identity resolution instead of hashed PII.
53
-
- Upload with manifest files rather than individual files so that the partitions of large files do not overwrite each other when using the FULL_REPLACE update strategy.
54
-
- Fix error parsing the Glue ETL parameter for timestamp_column when country_code parameter is unspecified
58
+
- Avoid dropping Country Code when LiveRamp, Experian, or Mobile Ad IDs are used for identity resolution instead of hashed PII.
59
+
- Upload with manifest files rather than individual files so that the partitions of large files do not overwrite each other when using the FULL_REPLACE update strategy.
60
+
- Fix error parsing the Glue ETL parameter for timestamp_column when country_code parameter is unspecified.
55
61
56
62
## [3.0.1] - 2024-06-21
57
63
@@ -67,7 +73,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
67
73
68
74
### Changed
69
75
70
-
- Migrated all AMC requests to use OAuth and the AMC API provided by Amazon Ads instead of instance-level APIs.
76
+
- Migrated all AMC requests to use OAuth and the AMC API provided by Amazon Ads instead of instance-level APIs.
71
77
- Migrated the front-end to align with the AMC API provided by Amazon Ads.
72
78
- Migrated the front-end to use the Amazon Cognito hosted user interface for login instead of AWS Amplify.
73
79
- Replaced time-series based file partitioning (which the AMC API no longer requires) with a strategy based on file size so that pseudonymized files will not exceed 500MB (compressed).
@@ -85,7 +91,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
85
91
## [2.3.0] - 2024-02-29
86
92
87
93
### Changed
88
-
94
+
89
95
- Provide country code when creating dataset in AMC.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+10-13Lines changed: 10 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,24 +6,23 @@ documentation, we greatly value feedback and contributions from our community.
6
6
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
7
7
information to effectively respond to your bug report or contribution.
8
8
9
-
10
9
## Reporting Bugs/Feature Requests
11
10
12
11
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
13
12
14
13
When filing an issue, please check [existing open](https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/issues), or [recently closed](https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
15
14
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
16
15
17
-
* A reproducible test case or series of steps
18
-
* The version of our code being used
19
-
* Any modifications you've made relevant to the bug
20
-
* Anything unusual about your environment or deployment
21
-
16
+
- A reproducible test case or series of steps
17
+
- The version of our code being used
18
+
- Any modifications you've made relevant to the bug
19
+
- Anything unusual about your environment or deployment
22
20
23
21
## Contributing via Pull Requests
22
+
24
23
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
25
24
26
-
1. You are working against the latest source on the *main* branch.
25
+
1. You are working against the latest source on the _main_ branch.
27
26
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
27
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
29
28
@@ -39,24 +38,22 @@ To send us a pull request, please:
39
38
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
40
39
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
41
40
42
-
43
41
## Finding contributions to work on
44
-
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/labels/help%20wanted) issues is a great place to start.
45
42
43
+
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/labels/help%20wanted) issues is a great place to start.
46
44
47
45
## Code of Conduct
46
+
48
47
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
49
48
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
55
52
53
+
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
56
54
57
55
## Licensing
58
56
59
57
See the [LICENSE](https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/blob/main/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
60
58
61
-
We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
62
-
59
+
We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
We take all security reports seriously. When we receive such reports, we will investigate and
4
-
subsequently address any potential vulnerabilities as quickly as possible. If you discover a potential
5
-
security issue in this project, please notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/) or
6
-
directly via email to [AWS Security](mailto:[email protected]). Please do not create a public GitHub issue in this project.
1
+
# Reporting Security Issues
2
+
3
+
We take all security reports seriously.
4
+
When we receive such reports,
5
+
we will investigate and subsequently address
6
+
any potential vulnerabilities as quickly as possible.
7
+
If you discover a potential security issue in this project,
0 commit comments