@juhoteperi I think you are the most likely to know this - I have now updated the packages for vega, vega-lite, vega-embed and vega-tooltip. These are all versions in support of the final release 3 of vega and release 2 of vega-lite. Newer are now dev rc versions.
@juhoteperi before I commit, should I remove the target
directories? Second, should I make four separate commits or all updates in one?
@jsa-aerial Yes, you should remove the target
directories. And probably better for clarity to have separate commits.
@miikka Thanks for the answers! I will remove the target dirs and make the separate commits. Should these also be separate pull requests or a single with the multiple commits?
I guess a single PR is fine.
@miikka I think there is something I do not understand about what the deps in the build.boot files mean. I am getting the error org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact cljsjs:vega:jar:3.3.1-0 in clojars (<https://repo.clojars.org/>)
, but that's because this 'commit' is supposed to build that (and the other new version) jars and deploy them there. So, I must have a kind of chicken/egg confusion about what the deps in the build files mean. I'm not a boot guy, so that may be a contributing factor...
Yes, you're right, sounds good. I didn't realize that there's the chain of dependencies for the libraries.
@miikka OK, it looks like we are on the right track - vega PR passed all checks. Does a 'blessed' maintainer need to now close the pull or do I close it and then a blessed maintainer merges and that is when clojars will be updated. I don't want to start adding vega-lite until I know this vega is totally completed as it will fail. Thanks for any info - thanks for patience - this is the first time I'm doing this...
Do not close it, a maintainer will merge it. I don’t have time today anymore, but I’ll check it tomorrow.
✔️ Thanks!