add anchor.js@1.0.6 w/ git autoupdate

[Piicksarn]

Checklist for Pull request or lib adding request issue follows the conventions.

Note that if you are using a distribution purpose repository/package, please also provide the url and other related info like popularity of the source code repo/package.

Profile of the lib

• Git repository (required): https://github.com/cbopp-art/anchor
• Official website (optional, not the repository): http://cbopp-art.github.io/anchor/
• NPM package url (optional):
• GitHub / Bitbucket popularity (required):
  • Count of stars: 34
  • Count of watchers: 4
  • Count of forks: 9
• NPM download stats (optional):
  • Downloads in the last day:
  • Downloads in the last week:
  • Downloads in the last month:

Essential checklist

• I'm the author of this library
  • I would like to add link to the page of this library on CDNJS on website / readme
• This lib was not found on cdnjs repo
• No already exist / duplicated issue and PR
• The lib has notable popularity
  • More than 100 [Stars / Watchers / Forks] on [GitHub / Bitbucket]
  • More than 500 downloads stats per month on npm registry
• Project has public repository on famous online hosting platform (or been hosted on npm)

Auto-update checklist

• Has valid tags for each versions (for git auto-update)
• Auto-update setup
• Auto-update target/source is valid.
• Auto-update filemap is correct.

Git commit checklist

• The first line of commit message is less then 50 chars, be clean and clear, easy to understand.
• The parent of the commit(s) in the PR is not old than 3 days.
• Pull request is sending from a non-master branch with meaningful name.
• Separate unrelated changes into different commits.
• Use rebase to squash/fixup dummy/unnecessary commits into only one commit.
• Close corresponding issue in commit message
• Mention related issue(s), people in commit message, comment.

close #6667, cc @cbopp-art

[Piicksarn]

@Amomo, would you please help me for checkout the pr?
Thank you!

[Piicksarn]

@maruilian11, would you mind to help me for checking the pr?
thank you!!

[maruilian11]

can you tell me how you told it's deprecated_GPL-2.0+ not GPL-3.0? i saw GPL-3.0 here.

[Piicksarn]

https://github.com/cbopp-art/anchor/blob/master/package.json#L16

[maruilian11]

i knew that, but if there is any uncertain object, we should at least open an issue then send the PR.

[PeterDaveHello]

Ping.

[Piicksarn]

@PeterDaveHello , i followed license.txt and modified the license part in package.json
Would you check it again?
Thanks

[PeterDaveHello]

@Piicksarn I'm okay with "deprecated_GPL-2.0+", have no idea about the reason to use "GPL-3.0" here, have you confirmed with the author? If you didn't, why not just follow its package.json?

[Piicksarn]

@PeterDaveHello, sure!

[PeterDaveHello]

@Piicksarn Let's rollback first, I don't want to have so many PR opened for a long time.

[PeterDaveHello]

@Piicksarn use "deprecated_GPL-2.0+" first.

[Piicksarn]

@PeterDaveHello , i have it modified and need u for taking a look! Thanks!

[PeterDaveHello]

Okay, finally ...