Changes for v0.12.3 (#67)

Author: thyagram-aws

.eslintrc.json

@@ -8,7 +8,14 @@
     "plugin:@typescript-eslint/recommended",
     "prettier"
   ],
-  "overrides": [],
+  "overrides": [
+    {
+      "files": ["test/**/*"],
+      "env": {
+        "jest": true
+      }
+    }
+  ],
   "parserOptions": {
     "ecmaVersion": "latest",
     "sourceType": "module"

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -1,5 +1,8 @@
 name: Bug Report
-description: Create a report to help us improve
+about: Create a report to help us improve
+title: ''
+labels: 'bug'
+assignees: ''
 body:
   - type: textarea
     id: description
@@ -90,6 +93,11 @@ body:
         - Safari/537.36
     validations:
       required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots to help explain your problem (please **DO NOT include sensitive information**).
   - type: textarea
     id: context
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -12,7 +12,7 @@ body:
   - type: textarea
     id: proposal
     attributes:
-      label: Describe the solution you'd like
+      label: Describe the feature you'd like
       description: A clear and concise description of what you want to happen.
     validations:
       required: true

.github/ISSUE_TEMPLATE/general-issues.md

@@ -0,0 +1,18 @@
+---
+name: "\U00002753 General Issue"
+about: Create a new issue
+title: ""
+labels: needs-triage, guidance
+---
+
+## :question: General Issue
+
+### The Question
+<!--
+Ask your question here. Include any details relevant. Make sure you are not falling prey to the [X/Y problem][2]!
+
+[2]: http://xyproblem.info
+-->
+
+### Other information
+<!-- e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,16 +1,5 @@
-## Issue \#
-<!-- If applicable, please link to issue(s) this change addresses -->
+*Issue #, if available:*
 
-## Description
-<!-- Why is this change required? What problem does it solve? -->
+*Description of changes:*
 
-## General Checklist
-<!-- Check or cross out if not relevant -->
-
-- [ ] Added new tests to cover change, if needed
-- [ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
-- [ ] Documentation update for the change if required
-- [ ] PR title conforms to conventional commit style
-- [ ] If breaking change, documentation/changelog update with migration instructions
-
-By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
+By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

.github/dependabot.yml

@@ -0,0 +1,10 @@
+# Basic `dependabot.yml` file with
+
+version: 2
+updates:
+  # Enable version updates for github-actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    # Check the actions for updates every week
+    schedule:
+      interval: "weekly"

.github/release.yml

@@ -19,5 +19,10 @@ yarn.lock
 *.tsbuildinfo
 *.tgz
 /src/config.ts
+.scannerwork/*
+deployment/open-source/
+deployment/regional-s3-assets
+deployment/global-s3-assets
+deployment/exclude-open-source-list.txt
 
 build

.github/workflows/build.yml

@@ -1,3 +1,6 @@
+// Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+// SPDX-License-Identifier: Apache-2.0
+
 module.exports = {
 	trailingComma: 'es5',
 	singleQuote: true,

.github/workflows/code-lint.yml

@@ -0,0 +1,8 @@
+# Use of opensource-codeofconduct email for amazon is expected
+CONTRIBUTING.md
+CODE_OF_CONDUCT.md
+
+.github/
+node_modules/
+coverage/
+.*/package-lock.json

.github/workflows/release.yml

@@ -0,0 +1,13 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.12.3] - 2025-02-28
+
+### Added
+
+- Updated GitHub link to https://github.com/aws-solutions/clickstream-analytics-on-aws-web-sdk 
+- Update gradle and fix vulnerabilities 

.github/workflows/test.yml

@@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+When filing an issue, please check [existing open](https://github.com/aws-solutions/clickstream-analytics-on-aws-web-sdk/issues), or [recently closed](https://github.com/aws-solutions/clickstream-analytics-on-aws-web-sdk/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
@@ -21,64 +21,6 @@ reported the issue. Please try to include as much information as you can. Detail
 
 
 ## Contributing via Pull Requests
-
-This is mostly the same as [GitHub's guide on creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
-
-First, create a _fork_ of `clickstream-web`. Clone it, and make changes to this _fork_.
-
-```shell
-git clone [email protected]:your_username/clickstream-web.git 
-```
-
-After you have tested your feature/fix, by adding sufficient test coverage, and
-validating Checkstyle, lint, and the existing test suites, you're ready to
-publish your change.
-
-The commit message should look like below. It started with a prefix like feat/fix or
-chore. After a paragraph describing what you've done, include links to useful resources. These might
-include design documents, StackOverflow implementation notes, GitHub issues,
-etc. All links must be publicly accessible.
-
-```console
-feat: add new preset event for screen view.
-
-Resolves: https://github.com/awslabs/clickstream-web/issues/222
-See also: https://stackoverflow.com/a/58662077/695787
-```
-
-Now, save your work to a new branch:
-
-```shell
-git checkout -b feature_page_view
-```
-
-To publish it:
-
-```shell
-git push -u origin feature_page_view
-```
-
-This last step will give you a URL to view a GitHub page in your browser.
-Copy-paste this, and complete the workflow in the UI. It will invite you to
-"create a PR" from your newly published branch.
-
-### Pull Request Guidelines
-- The title of your PR must be descriptive to the specific change.
-- The title of your PR must be of below format since next release version is determined from PR titles in the commit history.
-    - For a bugfix: `fix: description of changes`
-    - For a feature: `feat: add awesome feature`
-    - Everything else: `chore: fix build script`
-- No period at the end of the title.
-- Pull Request message should indicate which issues are fixed: `fixes #<issue>` or `closes #<issue>`.
-- If not obvious (i.e. from unit tests), describe how you verified that your change works.
-- If this PR includes breaking changes, they must be listed at the top of the changelog as described above in the Pull Request Checklist.
-- PR must be reviewed by at least one repository maintainer, in order
-  to be considered for inclusion.
-- PR must also pass the Actions like Checkstyle, Lint, and Unit tests.
-- Usually all these are going to be **squashed** when you merge to main.
-- Make sure to update the PR title/description if things change.
-- Rebase with the `main` branch if it has commits ahead of your fork.
-
 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
 
 1. You are working against the latest source on the *main* branch.
@@ -99,7 +41,7 @@ GitHub provides additional document on [forking a repository](https://help.githu
 
 
 ## Finding contributions to work on
-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' issues is a great place to start.
+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/clickstream-analytics-on-aws-web-sdk/labels/help%20wanted) issues is a great place to start.
 
 
 ## Code of Conduct
@@ -114,4 +56,8 @@ If you discover a potential security issue in this project we ask that you notif
 
 ## Licensing
 
-See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](https://github.com/aws-solutions/%%SOLUTION_NAME%%/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+
+We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes. 
+
+