9dfa0f4329
test: Add tests for Nextflow release version resolver
2024-02-03 18:53:03 -06:00
6403017471
feat!: Remove url resolver for NextflowRelease
2024-02-03 18:53:02 -06:00
aef834d8bc
feat!: Remove Octkit conversion function for NextflowRelease
2024-02-03 18:53:01 -06:00
c8b05abe99
test!: Remove testing utils for getting GitHub token
...
This is no longer needed under the new API.
2024-02-03 18:53:00 -06:00
c44d750e6f
chore!: Remove octokit throttling dependency
2024-02-03 18:52:59 -06:00
b51df5d41b
feat!: Remove Octokit API
2024-02-03 18:52:58 -06:00
d72644926c
refactor!: Replace Octokit API with nf-core API in main script
2024-02-03 18:52:57 -06:00
0e483a63dd
refactor!: Rename NextflowRelease.allBinaryURL to NextflowRelease.downloadUrlAll
...
Another API consistency update.
2024-02-03 18:52:56 -06:00
085e9ce75c
refactor!: Rename NextflowRelease.binaryURL to NextflowRelease.downloadURL
...
Another API consistency change.
2024-02-03 18:52:55 -06:00
9e1210850f
refactor!: Rename NextflowRelease.versionNumber to NextflowRelease.version
...
This is to preserve consistency with the new API
2024-02-03 18:52:54 -06:00
8e25d74dc3
feat!: Remove the "latest-*" version resolvers from get_nextflow_release
...
Not needed due to the new API
2024-02-03 18:52:53 -06:00
f6aadba037
fix: Fix the version number debug log
2024-02-03 18:52:52 -06:00
bad5f3ad62
test!: Remove version resolving tests for "latest*" versions
...
This functionality is now offloaded to the API.
2024-02-03 18:52:51 -06:00
714c30554f
feat: Make get_nextflow_release compatible with arrays
...
Although it seems like we're moving backwards, the new API only supports a
single data dump. I still like the iterative nature rather, so tack on
array support.
2024-02-03 18:52:51 -06:00
ba9bc8bd26
feat: Add nf-core website API wrapper
...
Basically, a stand-in for OctoKit, but smarter.
2024-02-03 18:52:50 -06:00
a1e3fd897a
feat: Add optional published_at field to NextflowRelease type
...
Per @ewels request, the API on nf-co.re includes a "published_at" field
with the date of each release. For future compatibility without breaking
anything current, add an optional field that can handle this additional
information.
2024-02-03 18:32:14 -06:00
3c145a195b
chore: Update CHANGELOG
2024-02-03 11:22:16 -06:00
4fb3dae2b8
chore: Add deprecation messages for GitHub API parameters
2024-02-03 11:22:16 -06:00
15cd07b8f0
chore: Update CHANGELOG
2024-02-03 11:20:30 -06:00
725f631c7c
chore: Update lint-staged config to also lint TypeScript files
2024-02-03 11:20:30 -06:00
0898720a28
chore: Initialize husky
2024-02-03 11:20:30 -06:00
73885d551e
chore: Install lint-staged
2024-02-03 11:20:30 -06:00
0512776f32
chore: Install husky
2024-02-03 11:20:30 -06:00
791b428d55
chore: Update CHANGELOG
2024-02-03 11:17:01 -06:00
5a8fee0c89
feat: Add working launch.json file for debugging in VSCode
2024-02-03 11:17:01 -06:00
d5ff89d8bb
feat: Add sourcemaps to tsconfig
...
This feature is needed by the VSCode debugger.
2024-02-03 11:17:01 -06:00
a46a611717
chore: Update CHANGELOG
2024-02-03 11:16:01 -06:00
b9e2acafe8
feat: Add actrc file
2024-02-03 11:16:01 -06:00
58b277c92b
feat: Add Java install if using act
...
For some reason, I need to pin the Java install when using act. This is not
needed when using the GitHub Actions runner, so add an escape clause to
only run this extra step when using act.
2024-02-03 11:16:01 -06:00
a0a0a4327f
refactor: Rename integration testing CI workflows to 'example-usage'
...
We have two CI workflows with the name "test" (three if you count
"test-14"). This ambiguates the job name, and results in act running both
unit tests and integration tests when running `act -j test`. Fix that by
changing the names.
2024-02-03 11:16:01 -06:00
ebae0f3159
chore: Update CHANGELOG for v1.5.1
2024-01-30 10:46:04 -06:00
c4fb7bfc75
chore: bump version in package json files
2024-01-30 10:44:39 -06:00
ba0bc84592
chore: Update CHANGELOG
2024-01-30 10:42:55 -06:00
3e5019b784
ci: Update minimum node version in ci
...
The pagination changes require Node.js 18 or greater, so update the test
apparatus to use the latest LTS version of Node.
2024-01-30 10:42:55 -06:00
da56dbefc9
test: Refactor API tests to work with combined functions
...
Now that we are lazy-loading the API pages, OctokitWrapper is handling the
conversion to NextflowRelease in one function call. This means we can't test
the API schema. That should be fine as we pinned the API version. We can
test that the resulting objects for validity, so do that.
2024-01-30 10:42:55 -06:00
67a9c84bd7
feat: Pin GitHub API version
2024-01-30 10:42:55 -06:00
a5dd242af1
feat!: Remove tag_filter function
2024-01-30 10:42:55 -06:00
2850a8553a
refactor: Replace pull_releases function with iterator generator
...
Although the types are different, the intent is the same, so I think the
name is fitting.
2024-01-30 10:42:55 -06:00
91ef9fb65a
test: Update testing framework to support iterators
2024-01-30 10:42:55 -06:00
737834224d
refactor: Swap list filtering with lazy iterations
2024-01-30 10:42:55 -06:00
2f9c53c090
fix: Make iterator work right
2024-01-30 10:42:55 -06:00
4af33538f0
feat: Add lazy release iterator
2024-01-30 10:42:55 -06:00
c71f252745
feat: Add using GitHub API latest feature back in
2024-01-30 10:42:55 -06:00
82d97e2453
refactor: Place latest stable release conversion inline
2024-01-30 10:42:55 -06:00
7473a3926d
refactor: Use callback for octokit conversion
2024-01-30 10:42:55 -06:00
251e9bd445
feat: Add larger pagination to octokit-wrapper
2024-01-30 10:42:55 -06:00
d52c98d592
chore: Bump version in CHANGELOG
2024-01-21 22:09:10 -06:00
77d8bbb78a
chore: Bump version is package.json to v1.5.0
2024-01-21 22:09:10 -06:00
2098c3cdb2
feat!: Remove manual API calling tests
...
These tests are no longer used since the switch to OctokitWrapper, and
conflict with packages required for the implementation of throttling, so
remove them.
2024-01-21 20:57:22 -06:00
8982670453
chore: Update CHANGELOG
2024-01-21 20:57:22 -06:00